While investigating issues relating to the SOI manager showing offline in the console, the Java console was enabled so that more diagnostic information would be reported.
The log contained this error
(javawsApplicationMain) [GlobalDefaultsClient.getConfigValue:64] (GLOBALDEFAULTS) - getConfigValue() failed; Manager may be offline. java.io.EOFException: Unexpected end of ZLIB input stream
(javawsApplicationMain) [GlobalDefaultsClient.getConfigValue:64] (GLOBALDEFAULTS) - getConfigValue() failed; Manager may be offline. java.io.EOFException: Unexpected end of ZLIB input stream
Exception in thread "Thread-29" java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at com.ca.sam.client.alarm.AbstractRootCauseTabPanel.getRootCauseSetting(AbstractRootCauseTabPanel.java:346)
at com.ca.sam.client.alarm.AbstractRootCauseTabPanel$GlobalConfigPoller.run(AbstractRootCauseTabPanel.java:130)
at java.lang.Thread.run(Unknown Source)
Release : 4.2
Component : Service Operations Insight (SOI) Console
Explanation of the problem from engineering:
This error does not cause the communication issue.
Whenever SOI manager was down, then sometimes the Root cause setting value was not coming from the manager configuration .
This has been fixed so if it is down, then it will not throw NumberFormatException
A fix for this will be included in SOI 4.2 CU2