Jump to content
JasperReports Library 7.0 is now available ×
  • This documentation is an older version of JasperReports Server Community Edition 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 Previous Releases

    For information regarding known issues found or addressed in Version 5 releases, see the 5.6.1 release notes.

    Current Known Issues

    Note that we have adopted new tracking numbers for our known issues. Issues listed in previous releases' notes include both the old and new numbers; new known issues list only the new numbers.

    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

    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. To work around this issue, edit the jasperreports.properties file. Comment out the net.sf.jasperreports.phantomjs.executable.path=path/to/phantomjs property, and increase the PhantomJS timeout by changing those settings to:

    com.jaspersoft.jasperreports.fusion.phantomjs.executable.path=path/to/phantomjs

    com.jaspersoft.jasperreports.fusion.phantomjs.executable.timeout=600000

    JRS-12507: The documentation for this release may refer to the release as 6.4.0. In such cases, the information applies to 6.4.0 and 6.4.2.
    JRS-11883: When the server is hosted by Tomcat 7.0.73 or Tomcat 8.0.39 and higher, and a user's name and organization are passed as a URL to the server, Tomcat returns an error reporting an illegal character. The problem is caused by the use of the pipe character (|) to specify the user name and organization ID. For example, Tomcat throws an error when the URL passed to the server includes:

    homeFlow&j_username=jasperadmin|organization_1

    This is because these versions don't allow the pipe character. Instead, you must use %7C as an escaped character; for example, you would instead use:

    homeFlow&j_username=jasperadmin%7Corganization_1
    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. With 5.1, Jaspersoft supports JBoss AS7/EAP6, but has uncovered issues with clone installs. For more information, see this article on our Community website.
    JS-30155 (was 33003): Export catalogs created through the web UI in JasperReports Server version 5.1.x contain incorrect metadata. When these catalogs re imported into JasperReports Server version 5.2, the objects they contain are created in the wrong location in the repository. To work around the problem, you must edit the catalog manually to edit a single line in a text file before importing it:
    1. Navigate the export catalog and locate the index.xml file.
    2. Open the index.xml file in a text editor and locate this text near the top of the file:

    <?xml version="1.0" encoding="UTF-8"?>

    <export><property name="pathProcessorId" value="zip"/>

    <property name="jsVersion" value="5.1.0 CE"/>

    <module id="repositoryResources"><folder>/public</folder>

    </module><module id="reportJobs"/></export>

    3. Update the jsVersion property to correctly identify the version of JasperReports Server that created the catalog. For example, change:

    <property name="jsVersion" value="5.1.0 CE"/>

    To:

    <property name="jsVersion" value="5.1.0 PRO"/>

    4. Save the file.
    5. Import the file into JasperReports Server.
    JS-30583 (was 43387): We are aware of a significant performance issues when the server is run in certain versions of. We recommend 8.5.20 or later.

    Known Issues Addressed in Previous Releases

    This defect, which was listed in the release notes of previous versions, was resolved in a previous release:

    JS-28160 (was 40543): We uncovered a number of issues while testing this release when deployed in Glassfish 3.1 that prevented us from supporting that specific version of Glassfish with previous releases. We have addressed this issue, though it requires additional configuration for non-clustered Glassfish 3.1.2.

    To change the configuration:

    1. Using a text editor, open the web.xml (found in <js-install>apache-tomcatwebappsjasperserverWEB-INF.
    2. Locate and uncomment (that is, remove <!-- from the beginning of) this line:

    <!--<listener-class>com.jaspersoft.jasperserver.core.util.GlassFishRequestContextListener</listener-class-->

    3. Locate and comment out (that is, add <!-- at the beginning of) this line:

    <listener-class>org.springframework.web.context.request.RequestContextListener</listener-class>

    4. Locate and uncomment these lines:

    <!--filtzer>

    <filter-name>GlassFishFilter</filter-name>

    <filter-class>com.jaspersoft.jasperserver.war.GlassFishSessionFilter</filter-class>

    </filter-->

    5. Locate and comment out these lines:

    <!--filter-mapping>

    <filter-name>GlassFishFilter</filter-name>

    <url-pattern>/*</url-pattern>

    </filter-mapping-->

    6. Save the file and restart the server.
    JS-31528 (was 44541): When the JasperReports Server installation executable ran in Windows against an existing Tomcat instance, it didn't remove the contents of the WEB-INF/lib directory, which resulted in duplicate JAR files that caused Tomcat to return errors and fail to initialize. This issue is resolved.

    These defects, which were listed in the release notes of previous versions, are considered obsolete:

    21798: When JasperReports Server is accessed through Microsoft Internet Explorer 8, performance may be impaired. Because this version of IE reached its end of life, we consider this defect obsolete.
    25258: When exporting your repository as part of the upgrade process from version 4.0.x, 4.1, or 4.2.x, an organization's theme is reset to the server's default theme. The workaround is to reset each organization's active theme. Custom themes may need to be upgraded, as described in the JasperReports Server Upgrade Guide. Because we have ended support for these versions, we consider this defect obsolete.
    32159: When the 64-bit JasperReports Server binary installer is run in some versions of Mac OSX (including Mac OSX 0.8.3), and you select the option to install the bundled PostgreSQL, an error appears if PostgreSQL 9.1 is already installed. Since we no longer certify this version of Mac OSX, we consider this defect obsolete. Note that this version of OSX is considered compatible with this version of the server.
    44576: Previous release notes suggested that JasperReports Server failed to export repository resources when the server was hosted by Glassfish 3 and higher and the web UI was viewed in Internet Explorer 9. We have determined that this issue was caused by incorrect configuration, and doesn't occur normally.

    User Feedback

    Recommended Comments

    There are no comments to display.



    Guest
    This is now closed for further comments

×
×
  • Create New...