I just upgraded from 20.1 to 20.3 and I get the following error in the OC
Nov 14 16:24:03:392 ERROR [attach_socket, com.nimsoft.nimbus.NimServerSession] (2) communication error, I/O error on nim session (S) com.nimsoft.nimbus.NimServerSession(Socket[addr=/10.152.74.154,port=49690,localport=48009]): End of stream while trying to read header at com.nimsoft.nimbus.NimSessionBase.recv(NimSessionBase.java:944) at com.nimsoft.nimbus.NimServerSession.recv(NimServerSession.java:90) at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.handleMessage(NimServerSession.java:145) at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.run(NimServerSession.java:123)Caused by: java.io.EOFException: End of stream while trying to read header at com.nimsoft.nimbus.NimSessionBase.readNimbusHeader(NimSessionBase.java:1080) at com.nimsoft.nimbus.NimSessionBase.recv(NimSessionBase.java:883) ... 3 more
Nov 14 17:26:18:244 ERROR [http-nio-80-exec-3, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/cabijs].[jsp]] java.lang.IllegalStateException: Cannot create a session after the response has been committe
Is this causing any error in the OC itself, or just seen in the logs?
In some cases this error can be the result of a firewall between the OC and CABI servers, so make sure the communication is fully allowed between OC and CABI.
But sometimes an error like this can also be a benign message as long as it is not associated with any unwanted behaviors.
It is also possible that this error would be resolved by applying the later updates to 20.3, eg. the October 2021 patch.
However, I would instead recommend continuning the upgrade through to 20.4x since 20.3 is no longer supported and then troubleshoot the issue only if it persists on the supported release.
Additionally, this error also appears
Nov 17 16:18:53:606 ERROR [http-nio-80-exec-8, com.ca.cabi4uim.jaspersoft.JasperRestClient] Failed to get : http://10.152.74.153:80/cabijs/rest_v2/resources?folderUri=/organizations/UIM/organizations/UIM/users&recursive=false&type=reportUnit&jaspertoken=7MOgSg6rvVOszEgxA3DWXShFCnr+vOAebZPbR5+6+7yFsyiWmKvYIVPEPapihou2??loq&orgidl=uim Nov 17 16:18:53:694 ERROR [http-nio-80-exec-8, com.ca.cabi4uim.controllers.CABIController] status code and response from jasper Nov 17 16:18:53:694 ERROR [http-nio-80-exec-8, com.ca.cabi4uim.controllers.CABIController] 404
As I wrote in the other thread, check if the fix in the Broadcom article (that is now only available in Google cache) is right for you. Also, some problems are solved with upgrade to a newer version.
This technical document provides a solution for an issue where the CABI Jasper Report Server crashes frequently.
Symptoms of this issue:
1. Regular crashes of the Jasper Report Server, leading to CABI content being unavailable in the UIM Operator Console.
2. Jasper Report Sever log file may display the below errors before the JRS shutdown command is triggered: (path: CA Business Intelligence\apache-tomcat\webapps\jasperserver-pro\WEB-INF\logs\jasperserver.log)
Caused by: javax.servlet.ServletException: java.lang.IllegalStateException: Cannot create a session after the response has been committed at org.apache.jsp.WEB_002dINF.jsp.modules.about.about_jsp._jspService(about_jsp.java:320) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:71)
ERROR EhCacheImpl,localhost-startStop-2:556 - -- JasperServer: EhCacheImpl shutdown called. This normal shutdown operation. ERROR EhCacheImpl,localhost-startStop-2:559 - -- JasperServer: EhCacheImpl calling cleanerTimer.cancel(). This normal shutdown operation. ERROR GenericExceptionMapper,https-jsse-nio-8443-exec-5:51 - Unexpected error occurs java.lang.NullPointerException
- UIM 20.3 / 20.3.1- CABI Jasper Report Server 7.1.1- Tomcat version: apache-tomcat-8.5.59
Set both JRE_HOME and JAVA_HOME server variables pointing to the jre provided with Broadcom's CABI Jasper Report Server installation: