This section describes issues you may need to be aware of, including:
For information about the status of specific cases, please visit TIBCO Jaspersoft Technical Support (http://support.tibco.com). For information regarding known issues found or addressed in Version 6 releases, see the 6.4.x release notes.
Current Known Issues
We're aware of these issues in this release of JasperReports Server:
| • | JRL-242 (was 17824): While Fusion Charts support annotations, JasperReports Server and Jaspersoft Studio don't support them. We may address this issue in a subsequent release. |
| • | JRS-15530: The UI Samples page for administrators, available in previous releases, has been removed. When testing themes and other cosmetic changes or customizations to the web UI, please navigate to a page with the component you're changing rather than viewing the samples page. We may address this issue in a subsequent release.
|
| • | JS-19100 (was 30018): When an XML/A provider returns data to the Ad Hoc Editor, JasperReports Server sometimes must convert the datatype to string. For example, an XML/A provider may return data of type currency; in an Ad Hoc view, such currency data is a string that displays as a symbol (such as $) and a number. When such an XML/A-based Ad Hoc view is saved as a report, its datatypes are converted again. JasperReports Server attempts to convert the data to their original types, but in some cases, such as currency, no such type is available, and so currency data is converted to type double. In reports created from an Ad Hoc view, XML/A data that was returned with datatype currency is displayed as a number; the currency symbol is omitted. Wei may address this issue in a subsequent release. |
| • | JS-30847 (was 43707): If a dashboard contains an image dashlet that relies on the repo: syntax to refer to its image, and superuser exports the dashboard (using the repository's Export context menu item or the Manage > Server Settings > Export page), the image isn't exported with the dashboard. We may address this issue in a subsequent release. |
| • | JS-32077: Multi-select input controls for reports treat the values as case-sensitive even if the data source is case-insenstive. |
| • | JS-33114: Exporting a report with large frame elements as an Excel spreadsheet may result in high memory usage, even when using a virtualizer. |
| • | JS-33304: Migrating from an earlier version of JasperReports Server with thousands of resources associated with an Oracle-based domain may result JasperReports Server being unable to edit the domain. |
| • | JS-34346: This release changes resource visibility constraints in multi-tenant deployments (that is, those that include more than one organization). The change disables certain cases of improper resource referencing, such as providing an absolute repository path (starting with the root organization) for a resource referenced in a report. If you have a reference to an image, a subreport, or other resource that has an absolute path (or uses a $P{} parameter that later resolves to an absolute path), the server returns an error. Please update such references to use path that are visible to users in the organization in question. Consider using relative paths, or use the public folder for reports used by multiple organizations. |
| • | JS-34721: Running node.js to optimize your JavaScript files results in the Visualize.js framework no longer working due to missing references in the optimized visualize.js script. |
| • | JS-34763: Exporting scheduled jobs in bulk results in an empty ZIP file. If you want to export scheduled jobs, you must export them individually. |
| • | JS-34767: Administrators in a attempting to import a file receive the following error message on the first attempt: "Import failed. Import of an organization to the root is not allowed." Importing the file a second time will be successful. Administrators in a multi-tenant organization can work around this issue by going to Manage > Server Settings and right-clicking Organization in the tree and choosing Import... to import the file. Administrators in a single-tenant organization must go through the import procedure twice in order to import a file. |
| • | JS-34837: Running an uploaded report that uses a non-existant table will result in an error. If you attempt to delete the organization that holds the report after running it, you will receive an error and will not be able to delete the organization. |
| • | JS-35409: Creating a domain using a virtual data source based on an Oracle data source may result in an error and the domain not being created. This is due to performance issues with virtual data sources using Oracle data sources. |
| • | JS-36540: The binary installer for this release does not run properly on Ubuntu 18.04. Clicking the Finish button at the end of installation does not close the installer. |
| • | JS-38006: The permissions window in the repository shows the Read + Write + Delete option twice in the drop-down list. |
| • | JS-41999: Changing an Ad Hoc View from table to crosstab may change the timestamp data due to incorrect categorizers for timestamps in the query. |
| • | JS-55770: JasperReports Server cannot be deployed as the root application in Tomcat. |
| • | JS-56033: Two identical Ad Hoc tables in a domain using different data sources may end up sharing the same cache, resulting in one of the tables displaying incorrect data. |
| • | JS-56039: This release will not allow you to open or edit a domain created in an earlier version JasperReports Server if it has a calculated field that refers to a field that no longer exists in the data source. |
| • | JS-56108: On AWS instances, the js-ant export and js-ant import commands may return unexpected errors when using options to specify import-export keys. Instead, use the js-export and js-import scripts (.bat on Windows or .sh on Linux) in the buildomatic folder. These scripts have been tested on AWS with the new options for import-export keys. |
| • | JS-56172: Support for the Groovy language in JRS has been upgraded to version 2.5.7. There is a documented issue with this version of Groovy, where expressions referencing objects of type java.util.Date can no longer use additional methods provided by Groovy. For example, the Groovy expression new Date().format('MM/dd/yy') would produce an error. This would affect Groovy code in domain security XML files or any DomEL expressions using the groovy() function. |
Known Issues Addressed in this Release
These defects, which were listed in the release notes of previous versions, were addressed in this release:
| • | JS-30677 (was 43514): We have found that earlier versions of PhantomJS may not support or include all the fonts JasperReports Server uses when exporting dashboards. For example: |
| • | If a dashboard contains fonts for certain locales (such as Japan and China), the text isn't rendered properly in the exported dashboard. |
| • | If a table in a dashboard has been filtered or sorted, the sort and filter icons aren't rendered properly in the exported dashboard. Sorted crosstabs exhibit similar behavior. |
The version of PhantomJS included with JasperReports Server 7.5 fixes these issues. If you continue to experience such issues, upgrade PhantomJS to at least version 2.0.
| • | JS-31493 (was 44499): The dual-measure tree map, tree map, and parent tree map chart types previously didn't support the hyperlink functionality when an Ad Hoc view or report is used in a dashboard. |
Known Issues Addressed in Previous Releases
These defects, which were listed in the release notes of previous versions, were addressed in a previous release:
| • | JA-926 (was 35986): When upgrading from earlier versions (such as 5.2), users had to take additional steps if they connected Jaspersoft OLAP's XML/A functionality to a remote JasperReports Server's XML/A sources. For more information, refer to the upgrade instructions for the latest version of JasperReports Server 5.6.x. |
| • | JRL-30: When JasperReports Server is hosted under certain combinations of Windows and application servers (such as WildFly 9 on Windows 8.1 or Tomcat 8 on Windows 10), the server becomes unresponsive when a user exports a report; the server responds again once the export completes. We added instructions for working around this problem to the JasperReports Server Administrator Guide. |
| • | JRS-11883: Some application servers, such as Tomcat, are ending their support of the pipe character (|), which is the delimiter between a user's name and organization when they are passed as a URL to the server; in this case, the application server returns an illegal character error. Our examples and documentation now use %7c instead of pipe. |
For example, instead of:
| homeFlow&j_username=jasperadmin|organization_1 |
we now use:
| homeFlow&j_username=jasperadmin%7Corganization_1 |
| • | JRS-15525: In the course of testing Wildfly 8.1 with earlier versions of JasperReports Server, we discovered issues that prevented the server from starting. Because the issues aren't present in later versions of WildFly, we have ended support for Wildfly 8.1. |
| • | JRS-15389: Some required and optional Tomcat configurations were mischaracterized in our user documentation. See the JasperReports Server Installation Guide and JasperReports Server Security Guide for corrected steps. |
| • | JS-20916 (was 32168): Though we didn't strictly support the practice, you could create a clone install of previous versions of JasperReports Server in JBoss. In more recent JBoss versions, issues with clone install of JasperReports Server force us recommend against their use. For more information, see this article on our Community website. |
| • | JS-30583 (was 43387): We are aware of significant performance issues when the server is run in certain versions of Tomcat. We no longer support version 8.0.x, and recommend 8.5.43 or later. |
| • | JS-32199: In previous versions of JasperReports Server, Domain security could be applied by checking user's attributes via the authentication.principal.attributes method of the REST API. Now, the authentication.principal.attributes method is no longer supported; discontinue its use in production and test environments. Instead, use the attributesService. |
For more information, refer to the JasperReports Server REST API Reference, as well as the JasperReports Server Security Guide section about updating your Domain security file to use attributesService.
Recommended Comments
There are no comments to display.