Jasper reports connection error after changing the Clarity default port

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

After changing the default http port (80) for Clarity to another value in CSA - Application Server - HTTP Port and restarting services, the Jasper reports fail to connect.

In the jasperserver.log file, connection errors such as "http 302" or "network connection failed" are seen.

Environment

Release: Any
Component: Clarity Jaspersoft

Resolution

The ports 80 and 443 are default parsed in the browser, so there is no need to add them in the "HTTP Entry URL" field in CSA (in a cluster, this is the URL of the front-end load balancer).

However, whenever you change this default port number for Clarity, it is recommended to add the modified port number also to the "HTTP Entry URL" field in CSA - Application Server: http://<servername>:<portnumber>

Although Clarity may recognize the port without this having added in the "HTTP Entry URL", other integrated components like Jasper will fail as they will continue to try connecting to the default port 80.

Best Practice is therefore to always add (even the default port 80) in the "HTTP Entry URL" field.

Additional Information

See also the Clarity Documentation, "Install Clarity", where you see the port added in the Entry URL:

The HTTP and HTTPS Entry URL fields for the server in CSA cannot be localhost when Jaspersoft is integrated with Classic PPM. When you use Jaspersoft, the URLs must be explicitly entered on the Application subtab of the Properties tab for the Classic PPM server. For example:
 HTTP Entry URL: http://<server name>:<port>
 HTTPS Entry URL: https://<server name>:<port>

See also: Jaspersoft / reports known issues with Clarity