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:
| • | 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.
|
Known Issues Addressed in this Release
These defects, which were listed in the release notes of previous versions, were addressed in this release:
| • | 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 later versions of WildFly, we have ended support for Wildfly 8.1. |
| • | 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.34 or later. |
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-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. |
Open topic with navigation
Recommended Comments
There are no comments to display.