Known Issues

The following issues exist in this release of JasperReports® Server:

Key Summary and Workaround
JS-69038

Summary: If JDK 17 is installed on a system, then installing JasperReports® Server using binary installer displays errors.

Workaround: Run JasperReports® Server in runtime mode on JDK 17 by performing the following steps:

  1. Delete or disable JDK 17 in the system (to disable, you can patch the PATH environment variable not to pick Java 17).
  2. Install JasperReports® Server using installer (it uses embedded JDK 8).
  3. Re-install or enable JDK 17 in the system.
JSS-3254

Summary: For report bursting, when the specified repository folder is non-existent, the folder is not created in the JasperReports® Server repository.

Workaround: None
JRL-1655

Summary: For AWS Athena, when a report with the WHERE clause is run in JasperReports® Server , the following error message is displayed:

net.sf.jasperreports.engine.JRException: Error preparing statement for executing the report query:

SELECT *

FROM sampledb.test

where sampledb.test.integer = ?

Workaround: Instead of using WHERE sampledb.test.integer = $P{Parameter1} ), provide the WHERE clause in the following format:

WHERE sampledb.test.integer = $P!{Parameter1}

JS-56392 Summary: REST Input Control creation uses a label as an ID.

Workaround: None
JS-62643 Summary: When executing an AdHoc report when JasperReports® IO is not up and running, the following error message is displayed: An unexpected error has occurred and 500 error code is displayed in the console.

Workaround: None
JS-62645 Summary: While executing AdHoc reports in JasperReports® IO and trying to apply any JIVE function, an empty error box, along with 500 error code in the console, is displayed.

Workaround: None
JS-62646 Summary: While executing AdHoc reports in JasperReports® IO when you cancel the report load and search for different text, 409 error code is displayed in the console the first time and later the page just displays Loading...

Workaround: None
JS-62647 Summary: While executing AdHoc reports in JasperReports® IO and restarting the JasperReports® IO server, the report keeps on loading and does not display any error message.

Workaround: None
JS-62674 Summary: While executing AdHoc reports in JasperReports® IO and navigating from viewing to editing mode in the dashboard, error are displayed in the JasperReports® IO logs.

Workaround: None
JS-62675 Summary: When using AdHoc reports in JasperReports® IO and exporting to XML using the /reports endpoint, .jrpxml is appended with the report name.

Workaround: None
JS-62676 Summary: When using AdHoc reports in JasperReports® IO and exporting to Excel/XLSX, the output in not generated in non-paginated format.

Workaround: None
JS-62826 Summary: When using AdHoc reports in JasperReports® IO and executing any AdHoc View report using invalid data source details, 500 error code is displayed in the console.

Workaround: None
JS-63394 Summary: When running a domain report in a suborganization in JasperReports® IO using Input Control, the following error message is displayed in JasperReports® IO logs: net.sf.jasperreports.engine.JRException: Resource not found at: /organizations/organization_1/qa_automation/Domains/Store.

Workaround: None
JS-63395 Summary: When using AdHoc reports in JasperReports® IO, an incorrect Response Content-Type generated for AdHoc View reports.

Workaround: None
JS-63396 Summary: When using AdHoc reports in JasperReports® IO, a proper error message is not displayed when an AdHoc report with deleted fields from a domain is run or included into a dashboard.

Workaround: None
JS-65363 Summary: In the Process Monitor dashboard, data loaded in the work report does not get updated as per the selection done in the work allocation report.

Workaround: None
JS-65548

Summary: When trying to deploy on Oracle on non-default SID (default SID is ORCL marked in oracle_master.properties), and using service name instead of SID, for example ServiceName=ORCLPDB, the command js-ant import-minimal-pro can return an exception such as:

" [java] 2022-03-25T18:03:02,863 ERROR IdTableHelper:105 - Unable obtain JDBC Connection org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory ([TibcoSoftware][Oracle JDBC Driver][Oracle]ORA-12505 Connection refused, the specified SID (ORCL) was not recognized by the Oracle server.)"

The issue is that even though you change the SID for jasperserver user, it has to be explicitly set separately for an auditdb user.

Workaround: Uncomment the line in default_master.properties and set the servicename:

audit.serviceName=ORCLPDB

JS-65890 Summary: For report bursting, the Excel output file is not generated after scheduling the burster report with bursting enabled.

Workaround: None
JS-66367 Summary: The dashboard filter does not work correctly all the time when charts with the filter are updated.

Workaround: None
JSS-3266 Summary: For report bursting, invalid parameter name has no validation.

Workaround: None
JS-62766 Summary: The Snowflake JDBC driver does not validate the non-existing or invalid or empty database during connection creation time when passing the db parameter in the connection URL.

Workaround: None
JS-62783 Summary: The Snowflake JDBC driver does not validate the warehouse.

Workaround: None
JS-63462 Summary: For Snowflake connector, a null Pointer Exception is shown when using a data source connection with an invalid host name.

Workaround: None
JS-60070 Summary: The domain created from data source using the MongoDB JDBC driver is not editable.

Workaround: None
JS-58890 Summary: Domain Security does not work for blocked users on Column Level Grants.

Workaround: None
JS-58922 Summary: Unable to edit domain when Full Outer Join is applied.

Workaround: None
JS-58860 Summary:The buildomatic JDBC driver property files for DB2, Oracle, and SQL Server data sources in JasperReports® Server9.0.0 contain references to old JDBC JAR files.

Workaround: Change the maven.jdbc.version property in the buildomatic files to the latest JDBC driver versions offered by the developers. You can find these files in the <js-install>/buildomatic/sample_conf/ directory.
JS-58540 Summary: When using Schemafilter to connect to MongoDB data sources, formats, such as regex, do not work.

Workaround: Use the ConfigOptions=Schemafilter=<database_name>:< collector_name> format.

JS-58316 Summary: The TIBCO Data Virtualization data source driver does not support using ORDER BY for Boolean columns in queries.

Workaround: None
JS-58285 Summary: When using the Neo4j JDBC data source for a domain, if the pre-filter uses a value with an apostrophe ('). then creating an is one of pre-filter for a table or crosstab returns an error.

Workaround: None
JS-58574 Summary: In recent versions of Mac OS, the Stop and Start scripts in the installation directory cannot be executed without Automator.

Workaround: None
JS-58145 Summary: Trying to use input controls for strings and integers for reports with a very large data size (for example, more than 100,000 rows) could result in the JasperReports® Server freezing in the Loading stage until the session is ended.

Workaround: None
JS-58144 Summary: If the input string contains a semicolon (;), dash (–), or number sign (#), the SQL validation for an Input Control could result in an error.

Workaround: None
JS-58065 Summary: Creating an ElasticSearch data source connection might result in an error when using JBoss EAP or WildFly app servers. By default, ElasticSearch data source connections are not available for JasperReports® Server and require additional configuration.

Workaround: None
JS-58055 Summary: The Safari browser often blocks access to the Visualize.js script because the script uses third-party cookies to enable cross-site access.

Workaround: See the JasperReports® Server Visualize.js Guide for workarounds for this issue.
JS-57772 Summary: Cannot log in to JasperReports® Server due to password length exception.

Workaround: Ensure that all app servers that participate in a cluster (or when app servers are configured to share the jasperserver repository database) are installed with the same keystore files. For more information, see Jaspersoft Community article.
JS-57748 Summary: Aggregations cannot be used on scalar functions in calculated fields when using an ElasticSearch data source.

Workaround: None
JS-57742 Summary: Table joins cannot be used in the domain when using an ElasticSearch data source.

Workaround: None
JS-57552 Summary: Using an asterisk (*) for the EndsWith and StartWith functions in the calculated fields results in errors when using an ElasticSearch data source.

Workaround: None
JS-57241 Summary: When an ElasticSearch data source is used in a virtual data source, the virtual data source only displays the Base tables of the ElasticSearch data source, not the views, when used in a domain.

Workaround: None
JS-41999 Summary: Changing an AdHoc View from table to crosstab may change the timestamp data because of incorrect categorizers for timestamps in the query.

Workaround: None
JS-34767 Summary: Administrators in an attempt to import a file receive the following error message on the first attempt: Import failed. The import of an organization to the root is not allowed. Importing the file a second time is successful.

Workaround: 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 to import a file.
JS-34346 Summary: 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.

Workaround: Update such references to use paths that you can view in the organization in question. Consider using relative paths, or use the public folder for reports used by multiple organizations.
JS-30847 (was 43707) Summary: If a dashboard contains an image dashlet that relies on the repo: syntax to refer to its image, and the superuser exports the dashboard (using the repository's Export context menu item or the Manage > Server Settings > Export page), the image is not exported with the dashboard.

Workaround: None
JS-19493 Summary: XML/A data sources return all datatypes to the AdHoc Editor as strings. When an XML/A-based AdHoc view is saved as a report, JasperReports® Server attempts to convert the data to their original types when the AdHoc view is saved as a report, but in some cases, such as currency, no such type is available. The currency data is converted to type double. The currency is displayed as a number and the currency symbol is omitted.

Workaround: None
JS-57551 Summary: Scalar functions cannot be used as a filter for AdHoc views when using an ElasticSearch data source.

Workaround: None
JS-57111 Summary: Incorrect date shown on AdHoc view with Oracle DATE datatype.

Workaround: None
JS-32077 Summary: Multi-select input controls for reports treat the values as case-sensitive even if the data source is case-insenstive.

Workaround: None
JRIO-707 Summary: Observed 500 error when an invalid parameter value is provided in the POST request body.

Workaround: None
JSS-3194 Summary: For jasperQL, aggregate functions are not getting applied on the fields and the column is being returned as blank.

Workaround: None
JRL-242 (was 17824) Summary: While Fusion Charts support annotations, JasperReports® Server and Jaspersoft® Studio do not support them.

Workaround: None