This section describes issues you may need to be aware of, including:
| • | Current Known Issues |
| • | Known Issues Addressed in this Release |
For information regarding known issues found or addressed in Version 5 releases, see the 5.6.1 release notes.
Current Known Issues
We're aware of these issues in this release of JasperReports Server:
| • | JA-926 (was 35986): If you use Jaspersoft OLAP's XML/A functionality to connect to a remote JasperReports Server's XML/A sources, you must take additional steps to complete your upgrade if your previous version was 5.2 or earlier. You must redefine your XML/A connections to specify the connection string in a new way. For example, in previous versions, the Foodmart XML/A connection specified: |
| Provider=Mondrian;DataSource=Foodmart |
In more recent versions, the DataSource portion of the connection string is always JRS when the remote provider is JasperReports Server. For example:
| Provider=Mondrian;DataSource=JRS |
Note that the final steps in this section, those regarding java.io.FilePermission, can be ignored.
| • | JRS-15525: In the course of testing Wildfly 8.1 with this version of JasperReports Server, we discovered issues that prevented the server from starting. Because the issues aren't present in Wildfly 8.2, which we already support, we have ended support for Wildfly 8.1. |
| • | 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 web page with the UI component you're changing rather than viewing the samples page. We may address this issue in a subsequent release. |
| • | JS-20916 (was 32168): Though we don't strictly support the practice, in previous versions of JasperReports Server, it was possible to create a clone install in JBoss by copying an existing JasperReports Server WAR file and deploying it to a new JBoss instance. Though Jaspersoft supports JBoss EAP6, we uncovered issues with clone installs. 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 recommend 8.5.30 or later. |
Known Issues Addressed in this Release
These defects, which were listed in the release notes of previous versions, were resolved in this release:
| • | 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 delimits a user's name and organization when they are passed as a URL to the server; 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: This Tomcat configuration, which was documented as optional, is required: |
| grant codeBase "file:/groovy/script" { permission java.io.FilePermission "${catalina.home}${file.separator}webapps${file.separator}jasperserver-pro${file.separator}WEB-INF${file.separator}classes${file.separator}-", "read"; permission java.io.FilePermission "${catalina.home}${file.separator}webapps${file.separator}jasperserver-pro${file.separator}WEB-INF${file.separator}lib${file.separator}*", "read"; permission java.util.PropertyPermission "groovy.use.classvalue", "read"; }; |
Note that the related JasperReports Server documentation has been corrected and moved from the JasperReports Server Security Guide to the JasperReports Server Installation Guide.
Recommended Comments
There are no comments to display.