Connection problems between cockpit and clients (daemons or interface) can have various causes. For this reason, a mechanism has been built into the web service calls that can react flexibly to certain exceptions with repetition. Which exceptions are interpreted as temporary connection problems can be configured in the Cockpit via "Administration" -> "Other settings" -> "List of known connection problems" (internal name: "known.connection.exceptions").
To be able to use the mechanism sensibly, the log level of com.innoface should be set to INFO. Here, you can see the abbreviated logging of a daemon that has been unplugged:
2021-02-08 12:00:02 WARN [pool-1-thread-2] AbstractWebServiceConnector:163 - Call of addTaskLoggingInfo(92175, ...) failed. Connection problem?
2021-02-08 12:00:02 WARN [pool-1-thread-2] WebServiceClient:282 - caught javax.ws.rs.ProcessingException -> RESTEASY004655: Unable to invoke request
2021-02-08 12:00:02 INFO [pool-1-thread-2] AbstractWebServiceConnector:178 - Reason of error was java.net.SocketTimeoutException. So retry call after 5 seconds
2021-02-08 12:00:09 WARN [pool-1-thread-3] AbstractWebServiceConnector:163 - Call of updateLifecycle(2525, ALIVE) failed. Connection problem?
2021-02-08 12:00:09 WARN [pool-1-thread-3] WebServiceClient:282 - caught javax.ws.rs.ProcessingException -> RESTEASY004655: Unable to invoke request
2021-02-08 12:00:09 WARN [pool-1-thread-3] WebServiceClient:282 - caught javax.ws.rs.ProcessingException -> RESTEASY004655: Unable to invoke request
2021-02-08 12:00:09 WARN [pool-1-thread-3] AbstractWebServiceConnector:249 - not connected
com.innoface.ece.ECEException: java.net.UnknownHostException: dekaifsrv40
at com.innoface.ece.webservice.rest.WebServiceClientRest.extractException(WebServiceClientRest.java:284)
at com.innoface.ece.webservice.rest.WebServiceClientRest.extractEceException(WebServiceClientRest.java:298)
at com.innoface.ece.webservice.SystemInformationManagerWebServiceFacade.serverTime(SystemInformationManagerWebServiceFacade.java:77)
at com.innoface.ece.webservice.AbstractWebServiceConnector.testConnection(AbstractWebServiceConnector.java:151)
at com.innoface.ece.webservice.AbstractWebServiceConnector.isConnected(AbstractWebServiceConnector.java:246)
...
.
2021-02-08 12:00:44 INFO [pool-1-thread-3] AbstractWebServiceConnector:215 - Next connection attempt in 40 seconds
2021-02-08 12:01:24 INFO [pool-1-thread-3] AbstractWebServiceConnector:226 - Successfully reconnected to server
2021-02-08 12:01:24 INFO [pool-1-thread-3] AbstractWebServiceConnector:192 - Connection established egain -> retry updateLifecycle(2525, ALIVE)
2021-02-08 12:01:24 INFO [pool-1-thread-2] AbstractWebServiceConnector:192 - Connection established egain -> retry addTaskLoggingInfo(92175, ...)
|
java.net.SocketTimeoutException is noted in the server as a known connection problem, so the calls are repeated at ever greater intervals until the connection is re-established.
