[java] ************** HibernateDaoImpl.executeWriteCallback EXCEPTION **********
[java] com.jaspersoft.jasperserver.api.metadata.common.service.JSResourceNotFoundException: jsexception.folder.not.found.at
[java] Arguments: "/organizations/organization_1/public",

Solution:

Export just the public folder from the community server. Open the archive with the public folder and find this property:

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

change it to:

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

Try to re-import to Professional version.

Issue:

While executing the below js-export.bat command from the <js-install>/buildomatic folder, the following error was encountered:

Command:

js-export.bat --everything --output-zip jrs-7.1-export.zip

Error:

Exception in thread "main" java.lang.NoClassDefFoundError: com/jaspersoft/jasperserver/export/ExportCommand

Solution:

The cause of this error was due to js-export.bat picking up an old unsupported version of java installed on the machine.  

A typical scenario would be having Java JDK 1.4.2 installed on the machine and its bin directory added to the front of the system PATH environment variable. 

The js-export.bat which runs the following command:

java -classpath "%EXP_CLASSPATH%" %JAVA_OPTS% com.jaspersoft.jasperserver.export.ExportCommand %JS_CMD_NAME% %CMD_LINE_ARGS%

would execute java under the incorrect JDK 1.4.2 bin directory. This is despite %JAVA_HOME% set to point to the correct version of Java (eg. C:Program FilesJavajdk1.8.0_161)

The solution is to remove the old version of Java from the system PATH environment variable, then open up a new command shell and first run "java -version" from buildomatic folder to ensure the right version of java is detected. Then run the js-export.bat command again.

Note:  This error can also occur with running js-export.sh as well as js-import.bat [.sh] scripts.

Note: This wiki article still applicable to Jasperserver v9.0

ref: 01852956

This article explains how to resolve the following upgrade validation error encountered while upgrading JasperReports Server from version 8.2.0 to version 9.0.0 using Microsoft SQL Server as the repository database.

Problem

During the upgrade process, the validation step fails with an error similar to the following:

[echo] Validating administrative database connection at jdbc:sqlserver://<server>:1433;...

BUILD FAILED

/app/production/FPI/jasperreports-server-pro-9.0.0-bin/buildomatic/bin/validation.xml:508:
The following error occurred while executing this line:

...
Error invoking getDriver() method

Cause

JasperReports Server does not bundle JDBC drivers for certain commercial databases, including:

• Microsoft SQL Server

• Oracle

• IBM DB2

When using one of these databases, the appropriate JDBC driver must be manually added before running the upgrade or installation process.

If the SQL Server JDBC driver is missing or incorrectly configured, Buildomatic cannot establish the repository database connection and the validation step fails with:

Error invoking getDriver() method

Solution

Step 1 — Obtain the SQL Server JDBC Driver

Download a compatible Microsoft SQL Server JDBC driver from Microsoft or use the driver already validated in your environment.

Example driver file:

mssql-jdbc-<version>.jar

Step 2 — Copy the Driver to the Required Directory

Copy the JDBC driver JAR file into the following directory:

<js_install>/buildomatic/conf_source/db/sqlserver/jdbc

Example:

/app/production/FPI/jasperreports-server-pro-9.0.0-bin/buildomatic/conf_source/db/sqlserver/jdbc

Step 3 — Verify default_master.properties

Update the database driver configuration inside:

<js_install>/buildomatic/default_master.properties

Ensure the SQL Server JDBC settings point to the correct driver.

Typical properties include:

dbType=sqlserver
jdbcDriverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver

Also verify:

• JDBC URL

• Database username/password

• Driver version compatibility

Step 4 — Re-run the Upgrade Validation

After placing the JDBC driver and confirming the configuration, re-run the upgrade command.

The validation step should now complete successfully.

Additional Information

For more details, refer to the following section from the official Upgrade Guide:

Working With JDBC Drivers

JasperReports Server Upgrade Guide - Working With JDBC Drivers

Summary

This issue occurs because JDBC drivers for commercial databases are not bundled with JasperReports Server distributions.

To resolve the issue:

1. Obtain the appropriate SQL Server JDBC driver

2. Copy it into the Buildomatic SQL Server JDBC directory

3. Verify default_master.properties

4. Re-run the upgrade validation process

This allows Buildomatic to successfully establish the repository database connection during the upgrade to version 9.0.0.
_________________________________________________________________________________________________________________________
Ref. Case #2550148

In TIBCO JasperReports® Server 7.5, the following exception is generated upon starting up the server :

log4j:ERROR Unexpected char [e] at position 17 in conversion patterrn.

How to resolve this error ?

Solution:

1. On the TIBCO JasperReports® Server, edit the file:

    ..webappsjasperserver-proWEB-INFapplicationContext-diagnostic.xml

2. Locate the following bean: 

   <bean class="org.apache.log4j.PatternLayout">
   

   and modify:

   <value>%-5p %c[1] - %m%ex%n</value>
   

   to delete the 'e' so it looks like this:

   <value>%-5p %c[1] - %m%x%n</value>
   

3. Restart the TIBCO JasperReports® Server.

Related Articles:

• JS-56613: Non critical exceptions in JRS startup
  
  Note: This issue is resolved in the JasperServer 8 version

We are using a map component from the 'Basic Elements' palette and have set the latitude and longitude values for the map center (under Map tab) to reference fields as $F{lat} and $F{long} respectively. 

However, when navigating to the Markers tab and adding a new marker or editing an existing marker, the map center latitude and longitude expression values were reset to 45.439722 and 12.331944 overwriting what was defined.

Solution:

This was reported as a defect (reference JSS-2682) and the workaround is to define all your markers first and then set/re-set the map center expression values last or copy and paste the relevant two lines back into the source code under the Source tab:

<c:latitudeExpression><![CDATA[$F{lat}]]></c:latitudeExpression> 
<c:longitudeExpression><![CDATA[$F{long}]]></c:longitudeExpression>

Issue:

We have exported reports and its dependencies from TIBCO JasperReports® Server 6.x and imported the reports into TIBCO JasperReports® Server 7.5. 

After trying to edit and run the imported report as a user (eg. jasperadmin) under the new organization, the following error appears to the user:

"There was an error on the server. Try again or contact site administrators. (ERROR UID: 8c6d4f7a-7dbb-4644-9db6-e07911accf55)" 

The ../WEB-INF/log/jasperserver.log file captured the following error:

2020-04-27T16:19:30,538 ERROR ErrorPageHandlerAction,https-jsse-nio-8443-exec-37:118 - Error UID 8c6d4f7a-7dbb-4644-9db6-e07911accf55
com.jaspersoft.jasperserver.multipleTenancy.MTResourceNotVisibleException: You may not access resources which do not belong to your organization.
...

Caused by: com.jaspersoft.jasperserver.multipleTenancy.MTResourceNotVisibleException: 
Path /organizations/<organization_name>/organizations/<suborg_name>/Data_Source/<DS_NAME> is not visible in organization context 

Note: The issue does not occur for the superuser account. 

Solution:

The error comes from a resource referenced from the report where there is an absolute path: 

/organizations/<organization_name>/organizations/<suborg_name>/Data_Source/<DS_NAME>

There were changes implemented in the TIBCO JasperReports® Server 7.x release where an absolute path referenced in report resource is no longer acceptable.

The solution is to update the affected resources to reference relative paths which is relative to the organization user.

In the TIBCO JasperReports® Server 7.5 Release Notes, the following statement was documented:

JS-34346: 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. Please update such references to use path that are visible to users 

in the organization in question. Consider using relative paths, or use the public folder for reports used by multiple organizations. 

ref: 01861769

I am trying to pass the MDX into a view through HTTP in URL but nothing happens and the MDX I'm passing gets rejected:

olap/viewOlap.html?name=/Renewals/some_view?mdx=select%20NON%20EMPTY%20{[Measures].[Max%20Effort],%20[Measures].[Contacts],%20[Measures].[Resp],%20[Measures].[$%20Resp],%20[Measures].[Pct%20Resp],%20[Measures].[Avg%20$],%20[Measures].[Premiums],%20[Measures].[Cost%20w%20Prem],%20[Measures].[Net%20w%20Prem],%20[Measures].[Net%20w%20Prem%20-%20Per%20Resp]}%20ON%20COLUMNS,%20%20NON%20EMPTY%20{([Expire%20Group].[Aug%202017],%20[Renewal%20Effort].[All%20Renewal%20Efforts],%20[Membership%20Tenure.Tenure].[All%20Tenures])}%20ON%20ROWS%20from%20[RenewalResponseCube]

Solution:

Characters [ ] { and } are illegal in a URL and need to be escaped.  Try to escape { with %7B, } with %7D, [ with %5B and ] with %5D


Addition explanation:

1. URL Specifications: According to RFC 3986 (the standard for URLs), characters like [ ] { } are classified as "unsafe" or "reserved" because they have special meanings in certain contexts or can be misinterpreted by web servers and browsers.

2. MDX Syntax: MDX relies heavily on these characters—square brackets [] for object names and curly braces {} for sets. If you don't escape them, the web server (like Apache Tomcat, which Jaspersoft usually runs on) may reject the request with a 400 Bad Request error before it even reaches the JasperReports application.

3. Correct Mappings: The hex codes provided in the solution are the standard URL-encoded (Percent-encoded) values:

• [ becomes %5B

• ] becomes %5D

• { becomes %7B

• } becomes %7D

Additional Recommendation

While the solution correctly identifies the brackets and braces, your original URL also contains spaces and commas. You should ensure the entire query string is fully encoded to avoid further "rejected" or "not found" errors.

A fully encoded version of your query parameter would look like this:

mdx=select%20NON%20EMPTY%20%7B%5BMeasures%5D.%5BMax%20Effort%5D%2C%20...

Tips for implementation:

• Browser Behavior: Modern browsers often "visually" show you the characters in the address bar, but they encode them behind the scenes. However, if you are generating this link via JavaScript or Java code, you must manually use a function like encodeURIComponent() (JS) or URLEncoder.encode() (Java) to ensure the query is safe.

Tomcat Security: If you still face issues after encoding, it may be because newer versions of Apache Tomcat (7.0.76+, 8.0.42+, 8.5.12+) are extremely strict. You might need to adjust the relaxedQueryChars attribute in Tomcat's server.xml if the server is still blocking these characters even when encoded.

The More information link under Advanced in the Format Visualisation tab does not work and opens the follow page:

Steps to Reproduce:

1. Create an Ad Hoc view

2. Change the Visualization Type to Column chart

3. Select the Format Visualization tab and click on the More Information link under Advanced section.

4. This would direct to an invalid page -> https://community.jaspersoft.com/wiki/advanced-chart-formatting

Solution:

This is a defect reported in the following incident:

JS-79001: Fix more information link in format visualization panel of adhoc designer

A fix for this is currently being developed amd targeted to an upcoming hotfix for JasperReports Server versions 9.0 and 10.0.0

Until the hotfix is available and applied, you can manually navigate to the correct URL which is:

https://community.jaspersoft.com/knowledgebase/best-practices/advanced-chart-formatting/

2. If user wants to use any custom location then they need to specify the path of the license file inside Tomcat/bin folder in setenv.sh or setclasspath.sh. They can follow the documentation for the same here Setting Up the JasperReports Server License

For example:

1. Copied the License file in /root or /jasperserver without setting anything in setenv.sh/setclasspath.sh in Tomcat/bin folder.
2. Placed the license in /opt folder where JRS installer and Tomcat were present. Then create one file setenv.sh in /opt/tomcat/bin and added the path of the license file as given below:--
export JAVA_OPTS="$JAVA_OPTS -Djs.license.directory=/opt"
Restarted Tomcat and JRS application.

We have reports designed with a table element that goes much wider then the page width.

We then created columns within the table that are automatically hidden at report generation.

In JasperReports Server 8.0, the report's table element would resize to the width of the table. However, when running the exact same report in JasperReports Server 9.0, the size of the table element is retained. This leaves a massive white space on the right hand side of the report output.

What is the difference between the two versions that is causing the table element to no longer reduce in size?

Solution:

This issue was caused by a defect.

We have a fix in JasperReports Server version 9.0 with followng description:

JSS-3580: Automatic resizing of table columns based on weights

Description:

When total visible columns width is different from table element width, the additional space left within the table box should be distributed among visible columns based on a weights system where columns with higher weight value get more of it.

Similarly, when table element width is smaller than visible columns total width, columns need to shrink and try fit into defined table box based on a weights system where columns with higher weights shrink more.

Columns that do not have weights specified are supposed to remain of fixed width.

The fix is included in the latest hotfix (or a hotfix same or newer than hotfix_JRSPro9.0.0_cumulative_20251204_0224). The readme.txt file under the jasperserver-pro sub-directory of the Hotfix zip should list the above defect.

Hotfixes can be downloaded from the support portal. 

On Windows Server, after starting up Tomcat service, we noticed the "Apache Commons Daemon Service Runner" process is taking up nearly all of the memory on the server.

How can we tune the Tomcat service to prevent this from occurring ?

Solution:

A cause to this could be that the java minimum heap size (-Xms) is set too high.

The recommendation is to tune the jvm to reduce on the minimum heap size and allow the memory to grow to the maximum heap size (-Xmx) when necessary.

1. If you had ran the bundled installer, then under Tomcat/bin folder and double click on:

jasperreportsTomcat.exe

Or if you installed Tomcat using an existing Windows service, look for an .exe file in the same location, with the same name as your Tomcat service

Or select the service from the Windows Start menu:

Start > Programs > Apache Tomcat > Configure Tomcat (Run as administrator)

2. In the Apache Tomcat Properties dialog, click on the Java tab.

3. In the Java Options field, enter only the options preceded by -X . Enter only one Java option setting per line.

For instance, add options as follows:

-Xms2048m

-Xmx9000m

Report execution containing a stored procedure failed with:

2026-02-26T11:16:38,005 ERROR SecureExceptionHandlerImpl,pool-18-thread-1:135 - There was an error on the server. Try again or contact site administrators. (Error UID: 09270dae-7e00-4229-b37c-95b59194450f). 
ERROR: relation "lg_bom_items_gb$tmp" does not exist

However when executing the same store procedure directly in the PostgreSQL database, it worked successfully.

Solution:

The error "relation does not exist" in PostgreSQL means the database cannot find the table you are referencing.

In this case, lg_bom_items_gb$tmp is a temporary table used during the data processing of the report execution.

Why this failed in JasperReports Server is because the JRJdbcQueryExecuter is in read-only mode by default and hence the lg_bom_items_gb$tmp temp table cannot be created.

These two JDBC parameters are required for the jdbc connection used by this report.

You can append these parameters below directly to your connection string to control session behavior.

readOnly=false

autoCommit=true

For example:

Modify the jdbc connection string as follows:

jdbc:postgresql://yourhost:5432/yourdb?readOnly=false&autoCommit=true

If the report is using a JNDI connection, then check the META-INF/context.xml and ensure the above two attributes are set.

Upon completing the build and starting up JBoss, the deployment of jasperserver-pro.war did not succeed.

The jasperserver-pro.war.failed log contains the following error:

"{\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"jasperserver-pro.war\\\".PARSE\" => \"WFLYSRV0153: Failed to process phase PARSE of deployment \\\"jasperserver-pro.war\\\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /opt/jboss/jboss-report/standalone/deployments/jasperserver-pro.war/WEB-INF/applicationContext-jms.xml
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /opt/jboss/jboss-report/standalone/deployments/jasperserver-pro.war/WEB-INF/applicationContext-jms.xml
    Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[7,1]

As a result, after starting JBoss with JasperReports Server, the failed deployment resulted in the /jasperserver-pro login page url returning a HTTP 404 status.

Solution:

It appears that the applicationContext-jms.xml file caused an issue with the JBoss deployment.

The purpose of this file is for the configuration of ActiveMQ java messaging service in a cluster deployment and if you are not using ActiveMQ then the file is not necessary.

Most of the content in the file is commented out by default.

As a workaround, delete or move the applicationContext-jms.xml out of the jasperserver-pro.war file and try the deployment again.

Problem statement-

Facing an issue while rendering a report in visuzlize js-

"Uncaught ReferenceError: visualize is not defined at display/?editorconsole=true:120:1" and "_display/?editor_console=true:1 Access to script at 'https://localhost:8443/jasperserver-pro/client/visualize.js' from origin 'https://fiddle.jshell.net' has been blocked by CORS policy: Permission was denied for this request to access the local address space."

The issue is reproducible even after adding 'domainWhitelist' and enabling 'https' from v9.0.

Solution-

We have investigated the behavior and found that it is related to recent security updates in modern web browsers, rather than an issue with the JasperReport Server.

The Issue: Local Network Access Restrictions

Modern browsers now actively block public domains (like jsFiddle) from accessing private domains or local networks. This security restriction, known as Local Network Access (LNA) permissions, was introduced in Chrome version 142 and is also enforced by Microsoft Edge and Mozilla Firefox.

Chrome: https://chromestatus.com/feature/5152728072060928

Edge: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-browser-policies/privatenetworkaccessrestrictionsenabled

Firefox: https://support.mozilla.org/en-US/kb/control-personal-device-local-network-permissions-firefox

While some configuration workarounds generally exist for CORS issues, they do not apply here. Because we load visualize.js via a script tag without a preflight call, setting the response header to Access-Control-Allow-Private-Network: true will not bypass the browser's block.

How to Resolve This

Because this is a browser-level security restriction, we highly recommend avoiding public platforms like jsFiddle when you need to communicate with a private or protected server.

To continue your work, please use one of the following workarounds:

1. Use a local HTML file (Recommended): Instead of running your code in jsFiddle, save and run your test code locally within an HTML file. This bypasses the public-to-private domain block.

2. Disable the LAN check in Chrome (Not Recommended): You can temporarily bypass this by navigating to chrome://flags/#local-network-access-check and disabling the flag. Please note: We do not recommend this due to security risks. Please consult with your security team to validate before disabling this flag.

When to use jsFiddle

You can still use jsFiddle without any issues as long as the communication is strictly between public resources. For example, in our Basic Report Embed demo, both jsFiddle and the mobile demo server are hosted on public domains, so the browser allows the connection.

- https://jsfiddle.net/8fhvw7zx/

25-Sep-2019 12:11:35.444 SEVERE [localhost-startStop-2] org.apache.catalina.core.StandardContext.startInternal 
One or more listeners failed to start. Full details will be found in the appropriate container log file
25-Sep-2019 12:11:35.444 SEVERE [localhost-startStop-2] org.apache.catalina.core.StandardContext.startInternal 
Context [/jasperserver-pro] startup failed due to previous errors

The jasperserver.log file contained the following :

2019-09-25 12:11:35,319 ERROR ContextLoader,localhost-startStop-2:331 - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jasperJMXServerConnector' 
defined in ServletContext resource [/WEB-INF/applicationContext-diagnostic.xml]: Invocation of init method failed; 
nested exception is java.io.IOException: Cannot bind to URL [rmi://localhost:10990/jasperserver-pro]: 
javax.naming.NameAlreadyBoundException: jasperserver-pro [Root exception is java.rmi.AlreadyBoundException: jasperserver-pro]
...
...
Caused by: java.io.IOException: Cannot bind to URL [rmi://localhost:10990/jasperserver-pro]: 
javax.naming.NameAlreadyBoundException: jasperserver-pro [Root exception is java.rmi.AlreadyBoundException: jasperserver-pro]

Solution:

The cause of the error is due to a conflicting diagnostic port 10990. 

This can occur if the server already has multiple installations of TIBCO JasperReports® Server where one was already successfully started.

The installation process does not provide a way to alter this internal port number.  

Steps to take post-installation :

1> Stop the Tomcat service

2> Locate and open the file js.diagnostic.properties located under ..webapps/jasperserver-pro/WEB-INF/

3> Modify the diagnostic port in the js.diagnostic.properties file from 10990 to a different port number such as 10995

4> Save the changes & Start the Tomcat service.

 Note: This is a specific use case and a solution that can be tried to resolve the issue

You've deployed a DataBricks JDBC driver into JasperServer and trying to connect to DataBricks environment. Upon trying to test connection you get an error:

org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Could not create a validated object, cause: [Databricks][JDBC](10220) Driver does not support this optional feature.

at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)

at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.testConnection(JdbcDataSourceService.java:85)

at com.jaspersoft.jasperserver.remote.connection.jdbc.JdbcConnector.testConnection(JdbcConnector.java:90)

...

org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)

Caused by: java.util.NoSuchElementException: Could not create a validated object, cause: [Databricks][JDBC](10220) Driver does not support this optional feature.

at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1191)

at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106) ... 190 more

Solution:

this is Apache DBCP is trying to auto-validate the connection which is something this driver doesn't support naturally. Try one of these approaches:

- add IgnoreTransactions=1; to the JDBC connection string

- edit <jasperserver WAR>/WEB-INF/applicationContext.xml, find the jdbcDataSourceServiceFactory and edit autoCommitUnsupportedDrivers and add <value>com.databricks.client.jdbc.Driver</value>, save the file and restart Tomcat.

You've created a report that includes an HTML5 chart. When trying to preview it in the studio the entire studio freezes and doesn't seem to do anything and you have to force shut down it.

Solution:

There may be a few sources of this problem. Try to eliminate them one by one:

1. Re-download and re-apply the license

2. Re-run studio with the -clean flag as described here: https://community.jaspersoft.com/documentation/jaspersoft%C2%AE-studio/tibco-jaspersoft-studio-user-guide/v900/jss-user-_-config-clean/

3. Try to explicitly configure the headless browser. To do so, configure the chrome executable property net.sf.jasperreports.chrome.executable.path in Window > Preferences > Jaspersoft Studio > Properties to point to local installation of Chrome

Issue:

After creating a Report Book and publishing it to the TIBCO JasperReports® Server, the Report Book is published successfully but after opening the Report Book, the message "Report is empty" is displayed instead of the actual contents. The sample Report Book, BookReport.jrxml provided as part of the sample project JasperReportsSamples also has this problem. 

When connecting to the server repository and looking at the published report book's source code (main.jrxml) in TIBCO Jaspersoft® Studio, it is noticed that there were parts missing. 

The version of TIBCO Jaspersoft® Studio is 6.4.0.

Solution:

The issue is a known defect in TIBCO Jaspersoft® Studio is 6.4.0 which is related to the following incident :

JSS-1615: Workbooks from the server cannot be opened in JSS 6.4.0 

 The solution is to download TIBCO Jaspersoft® Studio 6.4.2 or greater to resolve this issue. 

Users are unable to see the UUID type fields within the Domain Designer whenever Virtual Data Source is used. 

Enabling DEBUG for VirtualDataSourceQueryService captures the DDL with the uuid column (id) :

2019-07-24 14:22:38,589 DEBUG VirtualDataSourceQueryService,http-nio-8080-exec-16:253 - DDL FOR -1358264201 - Crim_DS_public :
CREATE FOREIGN TABLE applied_cd ( id object NOT NULL OPTIONS (NAMEINSOURCE '"id"', NATIVE_TYPE 'uuid'),

But the Domain Designer does not display the uuid column/s. There are no errors generated in the log.

Note that when creating a domain using JDBC data source, the UUID columns are displayed.

Solution:

For Virtual Data Source, SQL queries are validated against TEIID SQL and TEIID sees UUID fields as Objects.

We need to perform a mapping to map the object type to string.

In TIBCO JasperReports® Server version 9.0, edit the file.../WEB-INF/applicationContext-jdbc-metadata.xml 

and add the following mapping to bean "jdbcMetaConfiguration" under <property name="jdbc2JavaTypeMapping"> :

<entry key="JAVA_OBJECT" value="java.lang.String"/>

Note 1: This change requires a restart of the TIBCO JasperReports Server. 

ref: 01788075

ERROR HibernateDaoImpl,pool-14-thread-4:114 - ************** HibernateDaoImpl.executeWriteCallback EXCEPTION **********
org.springframework.orm.hibernate3.HibernateSystemException: could not serialize; nested exception is org.hibernate.type.SerializationException: could not serialize...
Caused by: org.hibernate.type.SerializationException: could not serialize...
Caused by: java.io.NotSerializableException: com.jaspersoft.jasperserver.export.modules.common.rd.DateRangeDTO...

Solution:

This usually happens when there are saved report options for certain controls that do not exist anymore or don't have that value as an option available.

The solution would be to unzip the repository archive,

Search for com.jaspersoft.jasperserver.export.modules.common.rd.DateRangeDTO and find the XML's describing these report option objects.

Save the list of these objects.

Remove their mentions from .folder.xml files of the folders where these resources are located.

Re-zip your archive and try to re-import.

Issue:

We have configured Tomcat 9.0.1 to use the APR/native connector with HTTP/2 upgrade protocol. Upon testing our main and drill down reports, the main report shows loading and again the "You must apply input values before the report can be displayed." message appears. In the catalina log file, we observed that the following StackOverflowError error was captured : 

01-Jun-2021 08:58:24.531 SEVERE [https-openssl-apr-443-exec-10] org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error reading request, ignored
 java.lang.StackOverflowError
    at org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:66)
    at org.apache.coyote.http2.AbstractStream.isDescendant(AbstractStream.java:70)
    ...

The <TOMCAT>/conf/server.xml has the following connector configuration:

    <Connector port="443" protocol="org.apache.coyote.http11.Http11AprProtocol"
               maxThreads="150" SSLEnabled="true" maxHttpHeaderSize="65536" >
        <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" writeTimeout="60000" readTimeout="60000" keepAliveTimeout="60000"/>
        <SSLHostConfig>
            <Certificate certificateKeyFile="conf/localhost-rsa-key.pem"
                         certificateFile="conf/localhost-rsa-cert.pem"
                         certificateChainFile="conf/localhost-rsa-chain.pem"
                         type="RSA" />
        </SSLHostConfig>
    </Connector>

Solution:

The issue is related to a HTTP/2 bug that is fixed in Tomcat version 9.0.2.

Refer to:

Bug 61682 - StackOverflowError while executing HTTP/2 Server Push

(https://bz.apache.org/bugzilla/show_bug.cgi?id=61682)

All fixes for Tomcat 9.0.x are listed in the change log :

https://tomcat.apache.org/tomcat-9.0-doc/changelog.html

In order to overcome the specific error, upgrading to Tomcat 9.0.2 or above is required. 

Note: If running on Tomcat 8.5, then the error is fixed in Tomcat 8.5.24 and above. (https://tomcat.apache.org/tomcat-8.5-doc/changelog.html)

Issue:

Running certain crosstab reports can result in the following error:

ERROR AsyncJasperPrintAccessor,pool-6-thread-4:321 - Error during report execution 
net.sf.jasperreports.engine.JRRuntimeException: Crosstab has not printed anything on 3 consecutive pages, likely infinite loop. 

Solution:

This is a defect reported in JRL-1249 and will be fixed in JasperReports^® Server 7.1.

The workaround is to set the following property in the ../classes/jasperreports.properties file:

net.sf.jasperreports.legacy.element.stretch.enabled=true

followed by a restart of the JasperReports® server.

Note: This issue affects versions 6.2.2 and higher.

Related Article:

JRL-1249: Crosstab infinite loop error

You have developed an HTML5 chart with a category label expression. After deploying the report to the TIBCO JasperReports^® Server through TIBCO JasperSoft^® Studio the category label expression does not appear. What to do?

Solution:

This may be related to a bug that was fixed in newer versions. If you encounter this problem, try to upload the report using the JasperReports^® Server UI instead.

1. In JasperReports Server, edit the report.
2. In first Set Up tab upload a local JRXML file. Point it to the the source code of your report
3. Save and run the report

When running the js-install script, it is failing with the error "Registry editing has been disabled by your administrator" followed by the following errors: 

C:\Jaspersoft\TIB_js-jrs_7.1.1_bin\jasperreports-server-pro-7.1.1-bin\buildomatic>js-install.bat minimal 
The system cannot find the file specified. 
The system cannot find the file specified. 
Could Not Find C:\Users\<username>\AppData\Local\Temp\3\_TEMP.REG 
=1-4* was unexpected at this time. 

We have locked down servers and it is unlikely that we can get registry editing permissions. 

How can we overcome this and complete the installation ?

Solution:

The installer needs to execute regedit for this reason explained in this article:

"TIBCO JasperReports® Server installer's usage of Windows Registry (Regedit)" (See Related Article 1)

It is best to allow the permission to edit the registry which can be guided in this article:

"How to Re-enable Windows Registry Editor when it is Disabled by Virus or Administrator" (See Related Article 2)

If this cannot be done, then you can follow Related Article 1 to customize the install scripts so that it doesn't call regedit but bear in mind the consequences of doing so, which is, "the result is that your log's file name might not be formatted to your system's exact day time and format."

Related Articles:

1.  https://community.jaspersoft.com/wiki/tibco-jasperreports-server-installers-usage-windows-registry-regedit

After upgrading Firefox browser to version 68.0.x, users have an issue with making a selection from the drop-down menu in the Ad Hoc View Panel.

The values cannot change when clicking on the drop down list.

Solution:

This is a client side defect that was reported in the following incident:

• JS-34685: Dropdown in Ad Hoc View not working with Firefox v.68

This defect is fixed in the major release, TIBCO JasperReports 7.5, which is available for download via TIBCO eDelivery. 

Until a fix is in place, the workarounds available are:

1. Use a different internet browser such as Chrome or Internet Explorer.

2. Use the UP/DOWN arrow keys from the keyboard to make the selection.

You can also import attached theme. This introduced CSS fix metioned in the comment section below

default_theme_720_js-34685.zip