"BMC-IMC810355E - Setting Connection status FAIL" seen repeatedly in the TrueSight Presentation Server 11.3.x cellservice.log file

Manage Support IDs

Use checkboxes to 'Remove support IDs/Users' or 'Allow to create Cases'
Support IDs for BMC Customer Support Site Guest User
Profiles Which Include    Back to All Support IDs
 

Knowledge Article

"BMC-IMC810355E - Setting Connection status FAIL" seen repeatedly in the TrueSight Presentation Server 11.3.x cellservice.log file
"BMC-IMC810355E - Setting Connection status FAIL" seen repeatedly in the TrueSight Presentation Server 11.3.x cellservice.log file
TrueSight Presentation Server
11.3.x

The following error is seen repeatedly (over 200 times) in the cellservice.log file on the TrueSight Presentation Server (TSPS). Are these indicative of a problem?

com.bmc.sms.imapi.gw.ImpactClientConnection [Receiving pncell_satsimp2646:PPM] Exception while receiving answer message: BMC-IMC810355E {\x00\x00\x00\x00\x00\x00\x00\x00}. Setting Connection status FAIL
com.bmc.sms.imapi.gw.ImpactClientConnection [Receiving pncell_satsimp2644:PPM] Exception while receiving answer message: BMC-IMC810355E {\x00\x00\x00\x00\x00\x00\x00\x00}. Setting Connection status FAIL
com.bmc.sms.imapi.gw.ImpactClientConnection [Receiving pncell_satsimp8946:PPM] Exception while receiving answer message: BMC-IMC810355E {\x00\x00\x00\x00\x00\x00\x00\x00}. Setting Connection status FAIL


source = /opt/bmc/TrueSightPServer/truesightpserver/logs/CellService.log
sourcetype = tsps
Using a load balancer between TSPS and TSIM is what is causing these exceptions in the log, but these messages do not cause any problems with functionality. Defect DRTSO-51241 has been opened to address this issue.
Defect DRTSO-51241 has been opened to address this issue.
These errors are harmless and have no impact on functionality.

Other probable reason for this behavior could be related to log4j, for this we can copy the cellservice.jar file from the backup made before TSIM upgrade and this could be another way for fixing this

If not, one extra solution could be to upgrade to a newer version
TrueSight Presentation Server
11.3.x
TrueSight Presentation Server
11.3.x
Attachment(s):