Jump to content
We've recently updated our Privacy Statement, available here ×

vchiem

Members
 View Profile  See their activity

  • Posts

    443

  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Security Advisories

Downloads

Everything posted by vchiem

  1. vchiem
    Issue:In version TIBCO JasperReports® Server 7.2, we have an issue deleting certain organizations. Instead a popup dialog box shows with the following error: Flush during cascade is dangerous; nested exception is org.hibernate.HibernateException: Flush during cascade is dangerous [/code]If we try to delete a User of the same troublesome organisation, we get an error message: Handler dispatch failed; nested exception is java.lang.StackOverflowError [/code]The jasperserver.log file captured the following: 2019-06-14 07:25:18,278 ERROR SecureExceptionHandlerImpl,ajp-bio-8009-exec-12:116 - Flush during cascade is dangerous; nested exception is org.hibernate.HibernateException: Flush during cascade is dangerous2019-06-14 07:25:27,139 ERROR SecureExceptionHandlerImpl,ajp-bio-8009-exec-12:116 - Handler dispatch failed; nested exception is java.lang.StackOverflowError2019-06-14 07:25:27,328 ERROR BasicLoggingFilter,ajp-bio-8009-exec-12:73 - Exception during flushing audit contextjava.lang.ClassCastException: java.lang.StackOverflowError cannot be cast to java.lang.Exception at com.jaspersoft.ji.logging.audit.util.ExceptionToAuditEventPropertyConverter.convert(ExceptionToAuditEventPropertyConverter.java:34) at com.jaspersoft.ji.logging.audit.context.AuditContextImpl.addPropertyToAuditEvent(AuditContextImpl.java:297)[/code] Solution:The reason for why the organization/s is in such state is unknown but it could be related to how the organization was created. For example, one scenario where it 'may' lead to such situation is when the organization was created by using PHP REST API. The normal use case is that organizations can be deleted by 'superuser' without any issues. There are dependent resources stored in JIAccessEvent table that are preventing the organization (or it's users) from being deleted successfully. The JIAccessEvent table stores access events based on user id. The workaround, depending on your requirement of the data in JIAccessEvent, is to either truncate the JIAccessEvent table or to carefully write a SQL query to identify the relevant rows pertaining to the troublesome organization and delete those rows (The tables to consider are JIAccessEvent, JITenant, JIUser). ref 01775967
  2. vchiem
    Search for this UID in the jasperserver.log under ../WEB-INF/logs as it may log further information in the form of a stack trace for you to determine what the cause may be.
  3. vchiem
    Issue:The following errors were observed during the deployment of TIBCO JasperReports® Server 7.2 on Websphere Application Server 8.5.5.15. [toc]Error Message: javax.servlet.ServletException: Filter [resourceHTTPHeadersFilter]: could not be initializedError Code: 500Target Servlet: com.ibm.ws.webcontainer.extension.DefaultExtensionProcessorError Stack: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/applicationContext.xml]; nested exception is java.lang.NoClassDefFoundError: org.w3c.dom.ElementTraversal at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:414) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) [/code] Solution: The TIBCO JasperReports® Server 7.2 Platform Support Guide explicitly specified 8.5.5.14 as the supported version for IBM Websphere (WAS). Upon investigation, there is a difference in the batik-all.jar file between versions 8.5.5.14 and 8.5.5.15 which can have an impact on the issue. For example, the batik-all.jar in WAS 8.5.5.14 has a file size of 4,253,697 bytes whereas WAS 8.5.5.15 has a file size of 4,262,889 bytes. Furthermore, in WAS 8.5.5.15 there may (possibly) exist file xml-apis-2.10.0.jar which is not resident in 8.5.5.14. Both these two files upon inspection contains the org.w3c.dom.ElementTraversal class which can be a cause of conflict. The solution is to revert to a certified version of Websphere 8.5.5.14. Note: Should you encounter this exception for WAS 8.5.5.14, refer to the related article below. Related Articles: https://community.jaspersoft.com/wiki/issues-deploying-and-starting-tibco-jasperreports-server-72-websphere-application-server ref: 01780624
  4. vchiem
    Issue:After deploying TIBCO JasperReports® Server 7.2 on Websphere Application Server installed on Windows, starting the JasperReports® Server failed and the SystemOut.log file captured the following exceptions : [toc][26/6/19 11:29:40:367 SGT] 00000094 ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0271E: Uncaught init() exception created by servlet [jasperserver] in application [jasperserver-pro_war]: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'themeSource' defined in ServletContext resource..Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xxxxxxxx' defined in ServletContext resource..Caused by: org.hibernate.boot.InvalidMappingException: Could not parse mapping document: null (INPUT_STREAM)..Caused by: java.lang.ClassCastException: com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory incompatible with javax.xml.stream.XMLInputFactory at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)[/code]Solution:The exceptions are due to a class conflict from the existence of the file ../WEB-INF/lib /xml-apis-1.4.01.jar. The instructions in the TIBCO JasperReports® Server 7.2 Installation Guide has a step on page 71 to remove xml-apis-1.4.01.jar (in addition to other files from the jasperserver-pro.war). 9. Enter the following additional commands:cd <js-install>zip -d jasperserver-pro.war WEB-INF/lib/stax-api-1.0.2.jarzip -d jasperserver-pro.war WEB-INF/lib/jta-1.1.jarzip -d jasperserver-pro.war WEB-INF/lib/xml-apis-1.4.01.jarzip -d jasperserver-pro.war WEB-INF/lib/javax.el-2.2.4.jarzip -d jasperserver-pro.war WEB-INF/lib/javax.el-api-2.2.4.jarzip -d jasperserver-pro.war WEB-INF/lib/batik*[/code]However, these commands will not work on a Windows platforms and Windows users will need to manually remove these individual files from the ../WEB-INF/lib directory. In addition to step 9, the following step 10b is necessary, otherwise users may see an error similar to : Caused by: java.lang.NoClassDefFoundError: org.w3c.dom.ElementTraversal[/code]10. Add the latest batik-all.jar from Websphere:b. Copy the file into a lib directory in the jasperserver-pro.war file, for example:cd <js-install>mkdir -p WEB-INF/libcp /opt/IBM/WebSphere/AppServer/systemApps/isclite.ear/lib/batik-all.jar WEB-INF/lib"%JAVA_HOME%binjar" uf jasperserver-pro.war WEB-INF/lib/batik-all.jar[/code]Since this step will not work because the 'cp' command is not recognized on Windows, users can use Windows Explorer to copy the Websphere packaged batik-all.jar from: C:/Program%20Files%20(x86)/IBM/WebSphere/AppServer/systemApps/isclite.ear/lib to C:/Program%20Files%20(x86)/IBM/WebSphere/AppServer/profiles/WAS85514_AppSrv02/installedApps/DESKTOPNode03Cell/jasperserver-pro_war.ear/jasperserver-pro.war/WEB-INF/lib and restart Websphere. Note: A documentation enhancement request (JS-34675) has been filed to provide clearer instructions for WAS installed on Windows platform. Related Articles:JS-34675: Installing WAR file for Websphere needs instructions for Windows installationJRS-20130: Libraries Upgrade - JRS deployment fails on Websphere 8.5.5.14 with error "java.lang.ClassCastException: com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory incompatible with javax.xml.stream.XMLInputFactory" ref: 01780624
  5. vchiem
    Issue:When scheduling report jobs with email notifications enabled, the email notifications failed to be sent. The jasperserver.log file generated the following exception: [toc]2019-07-05 15:13:36,919 ERROR SecureExceptionHandlerImpl,quartzScheduler_Worker-1:116 - The job error notification was not completed. An error occurred while sending it.2019-07-05 15:13:36,924 ERROR ReportExecutionJob,quartzScheduler_Worker-1:366 - The job error notification was not completed. An error occurred while sending it.org.springframework.mail.MailAuthenticationException: Authentication failed; nested exception is javax.mail.AuthenticationFailedException at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:425) ...Caused by: javax.mail.AuthenticationFailedException at javax.mail.Service.connect(Service.java:306)[/code]We set the mail.debug to true for further javamail debugging (under <property name="javaMailProperties">): <prop key="mail.debug">true</prop> in the applicationContext-report-scheduling.xml and this error is then logged to the console: DEBUG SMTP: Attempt to authenticateAUTH LOGIN334 VXNlcm5hbWU6YWRtc2NoZWR1bGVyQGdtYWlsLmNvbQ==334 UGFzc3dvcmQ6dmNoaWVtMTIz535-5.7.8 Username and Password not accepted.[/code]However, we have checked the SMTP configuration in the files applicationContext-report-scheduling.xml and js.quartz.properties and the username and password are correct. We can even log in directly to the GMail account outside of Jaspersoft using these credentials without any problems. Solution:If the username and password is incorrect, the same authentication failed exception would also occur but in this case where the username and password were already successfully validated, the cause of this error is actually not with the username or password but in the Gmail account where the option "Allow less secure apps" is turned OFF (This is turned off by default). You can find this setting in the Security section after logging into the GMail account. However, even with this setting enabled, if the GMail account is configured with "2-Step Verification" enabled, the Authentication failed exception will also be thrown with a different SMTP error message: DEBUG SMTP: Attempt to authenticateAUTH LOGIN334 VXNlcm5hbWU6YWRtc2NoZWR1bGVyQGdtYWlsLmNvbQ==334 UGFzc3dvcmQ6dmNoaWVtMTIz534-5.7.9 Application-specific password required[/code]Therefore, in order for this to work, "2-Step Verification" needs to be turned off as well.
  6. vchiem
    If jrxml chart is an option then see attached for example. Main step is the advanced properties tab to make the type an 'spline'. But Ad Hoc chart has more limiting capabilities so I am not sure whether it can be applied to the Ad hoc.
  7. vchiem
    Try doing a complete uninstall of Studio and then a re-install under an account with administrator privileges.
  8. vchiem
    The Mobile Guide is there in one of the older releases. To be specific its under Android v1.7. The Web Services guide is there too for REST implementations.
  9. vchiem
    Issue:When using the ElapsedDays function in a calculated field of an Ad Hoc View to calculate the elapsed days between two dates, the resulting value unexpectedly returns a decimal value rather than an integer. For example: ElapsedDays function is used to subtract the difference between the following dates: Date 1 = 10-FEB-2017 12:00:00 Date 2 = 01-APR-2017 12:00:00 and the result returned is 49.96 instead of 50. How can we make this function return an integer value ? Solution:The ElapsedDays function have been from the start and will always return a decimal value. Although users would typically perceive the function to return the number of days as a whole integer value, changing this to return an integer type may have adverse consequences to users who have already been using this function extensively in their application. Technically, ElapsedDays function is doing the right thing by returning decimal because when you pass a date timestamp (see above example dates) it also has time component (hours, minutes, secs). So there will be no integer elapsed days but decimal (days + part of the day presented by time in timestamp). The simplest way to display the result as an integer representation is to use the available Ad Hoc data mask format. See below illustration on how to change the format display for calculated field 'DaysPassed' which uses ElapsedDays function: Related Articles:JS-25068: Calc Fields and Measures: ElapsedDays returns a floating result 6,486.48
  10. vchiem
    Issue:When updating an existing user's properties such as adding or editing email address and/or adding roles, the previouspasswordchangetime field in the table jiuser is updated to a null value despite the existence of a previous value. The expected outcome is that it should retain the previous data since the password was not changed. Solution:Updating a user's email address or roles should not reset the previouspasswordchangetime to null. This was reported as a defect with the following incident reference: JS-34646: updating existing user properties resets previousPasswordChangeTime to null which is targeted for a future release of TIBCO JasperReports® Server. Until this is addressed, a workaround option is to use REST api to update the user's properties. Example of using REST to update properties of 'joeuser': Note: The above interface is a snapshot of using 'Postman' tool for REST implementations. It is configured with 'superuser' for Basic Auth headers ref: 01779294
  11. vchiem
    The Mobile Guide is there for download in one of the older releases when you expand. https://community.jaspersoft.com/project/tibco-jaspermobile-sdk-android/releases https://community.jaspersoft.com/project/tibco-jaspermobile-sdk-ios/releases
  12. vchiem
    The Mobile SDK is a community provided project only and all that is available are through these links below. There is no commercial support for it. The Mobile Guide is there for download in one of the older releases when you expand. https://community.jaspersoft.com/project/tibco-jaspermobile-sdk-android/releases https://community.jaspersoft.com/project/tibco-jaspermobile-sdk-ios/releases
  13. vchiem
    There are 2 errors here. For first error, ensure the owner of the table qrtz_fired_triggers is the username specified in the buildomatic default_master.properties file. You can determine the owner of the table by entering pgAdmin and looking at the table properties. The second error appears to relate to a permissions issue. Check whether the install is done under an admin account or whether the file to be copied or deleted is opened/in-use, locked etc.
  14. vchiem
    Please review this article: https://community.jaspersoft.com/wiki/license-file-corrupt
  15. vchiem
    Issue:We find that TIBCO Jaspersoft® Studio is not tagging the reading order for JRXML reports correctly when exporting to PDF output. We have tested the exported PDF documents using Acrobat's "Read Out Loud" function and in some cases, our PDF reports were incorrectly read from the right side to the left side of the page. However, for PDF exported from Ad Hoc Views, the reading order is correct. How do we control the order that PDF reports are tagged for 'reading order' ? Solution:The reading order corresponds to the order of the elements in the Outline view of the TIBCO Jaspersoft® Studio. This is the Outline pane on the left in Design mode. The re-ordering of the elements under each Band can be done simply by dragging the elements up or down in their correct position with the order starting from the top.
  16. vchiem
    Issue:In TIBCO JasperReports® Server 6.2.0, we have scheduled reports that outputs the file as '<filename>.nopag.xlsx' format but after upgrading to TIBCO JasperReports® Server 7.1.0, the filename generated is '<filename>.xlsx' without the 'nopag' prefix. Our xlsx pagination setting is set to false. Please explain why we are seeing such differences in behaviour ? Solution:This design behaviour was changed in TIBCO JasperReports® Server 6.3.0. Before release 6.3.0, users were reporting the 'nopag.xlsx' as an issue and wanted to have this 'nopag' prefix removed. It was removed through defect incident: JS-17864: Non-paginated xlsx exports have file extension of .nopag.xlsx The file extension was hardcoded in the source code: jasperserverjasperserver-api-implenginesrcmainjavacomjaspersoftjasperserverapiengineschedulingquartz XlsNoPaginationReportOutput.java where it got removed and from 6.3.0 onwards, scheduled report jobs that outputs non-paginated xlsx will no longer have the 'nopag' prepended to the filename.
  17. vchiem
    Issue:We are using Spring framework with spring-beans 5.x and when doing report compilation the following error occurred: [toc][jar:file:/<jar_location>/jasperreports-highcharts-6.4.1.jar!/com/jaspersoft/jasperreports/highcharts/component_beans.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 28; cvc-complex-type.3.2.2: Attribute 'local' is not allowed to appear in element 'ref'.......Caused by: org.xml.sax.SAXParseException; lineNumber: 10; columnNumber: 28; cvc-complex-type.3.2.2: Attribute 'local' is not allowed to appear in element 'ref'.at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unknown Source)[/code]The issue has been reported for TIBCO JasperReports® Library versions 6.4.1, 6.5.1, 7.1, 7.2. Solution:With TIBCO JasperReports® Library releases 7.2 and earlier, the distribution of JasperReports High Charts component works with Spring 3.x and the error arises from the incompatibility with Spring version 5.x. This is addressed with the release of TIBCO JasperReports® Library Pro 7.3.0 which is distributed as part of the TIBCO JasperReports® Server 7.2.0 product suite. Related Articles:JRL-1284: JR HighCharts component relies on Spring 3.xhttps://community.jaspersoft.com/questions/1085721/exception-jasperreports-651-spring-503
  18. vchiem
    Issue: We have an input control to show a list of values, but the width of the input control is insufficient to show the full values. As illustrated below, the width of the last input control is resized to the length of the label 'Version' causing the values in the dropdown list to be truncated. It should be resized to the length of the longest value. Solution:This is a known defect that is an issue only for 'Top of Page" input controls. The incident reference is: JS-33483: Input controls are more compacted or squished in JRS 6.4.0 compared to 6.2.1 The defect is fixed in the TIBCO JasperReports® Server 7.2 release which is currently available for download. As a workaround, you can try padding the Input Control label name with spaces as the width is adjusted to the label name or you can use other display modes such as "In Page" or "Pop up".
  19. vchiem
    Issue:Upon executing a job with the tSAPTableInput component, the following error was encountered: What steps must be taken to resolve this problem ? Solution:The error complains about Z_TALEND_READ_TABLE not being available because you have to install this SAP function module first. To use the custom function Z_TALEND_READ_TABLE, you need to install a SAP module provided under the directory <Talend_Studio>pluginsorg.talend.libraries.sap_<version>resources. For how to install the SAP module, see the file readme.txt under the directory. For more information, please review the following document on how to install the Z_TALEND_READ_TABLE function module : "How to install a Talend Function module for SAP" (See link provided under 'Related Articles') Related Articles: https://help.talend.com/reader/Cx7h_UFQ1sRfvxPVp64siw/ShpvhVG~qJG34GFsw3fIHQ
  20. vchiem
    There is no formal standard practice for report development as you can approach it either way as long as you know that by creating a query in a dataset with a parameter, there must exist a parameter defined. If the query is created first with a parameter, it will obviously error with parameter does not exist but the parameter can be created afterwards and then go back to the dataset query to verify it without needing to write the query again. However, if the parameter is included initially you cannot preview the resultset of the query written, so you can write a query that doesn't include any parameters first to preview the result and then include the parameter afterwards..after it being defined and then injected into the SQL.
  21. vchiem
    Audit Logging of user activity are stored only in auditing tables.
  22. vchiem
    5.0 to 7.1 is across 2 major releases. There would have been schema / repository changes since. Thats why our upgrade guide suggests a two step upgrade when going to 7.1. First to 6.4.x and then from 6.4.x to 7.1.x
  23. vchiem
    Best to explore the available properties from here: http://jasperreports.sourceforge.net/config.reference.html#net.sf.jasperreports.text.save.line.breaks such as: net.sf.jasperreports.text.save.line.breaks net.sf.jasperreports.export.pdf.force.linebreak.policy
  24. vchiem
    On the server, there is the jasperserver.log under WEB-INF/logs. Should check this to see what exceptions are being logged. Maybe its phantomjs that is required to be installed and configured on the server...this is a guess only. Refer to the Jaspersoft Admin guide for info on phantomjs
  25. vchiem
    The closest feature Jaspersoft have is the Audit Trail which may do at least some of what you want. But the Community edition does not have this since it is a licensed feature. Check this table for editions that does have it. https://www.jaspersoft.com/editions
×
×
  • Create New...

© 2024 Cloud Software Group,
Inc. All rights reserved.

Products

Explore