Jump to content
JasperReports Library 7.0 is now available ×
  • This documentation is an older version of JasperReports Server Release Notes. View the latest documentation.

    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:


    In more recent versions, the DataSource portion of the connection string is always JRS when the remote provider is JasperReports Server. For example:


    JRS-12507: The documentation for this release may refer to it using its previous version numbers, such as 7.1.1. In such cases, the information also applies to 7.1.3.
    JRL-242 (was 17824): While Fusion Charts support annotations, JasperReports Server and Jaspersoft Studio don't support them. Annotations cannot be used in Pro Charts. We plan to address this issue in a subsequent release.

    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-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. We plan to 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.43 or later.
    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.

    If you experience such issues, upgrade PhantomJS to at least version 2.0.

    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 plan to address this issue in a subsequent release.
    JS-31493 (was 44499): The dual-measure tree map, tree map, and parent tree map chart types don't currently support the hyperlink functionality when an Ad Hoc view or report is used in a dashboard. We plan to address this issue in a subsequent release.
    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.

    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:


    we now use:

    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.

    User Feedback

    Recommended Comments

    There are no comments to display.

    This is now closed for further comments

  • Create New...