We are periodicly receiving alerts that one of our Process Servers goes into a connecting status and then immediatly goes back into a running status. We are running M33.85.
The process server is configured with with the following services
- JobChainService
- SAPR3Service
- PlatformAgentService
I'm thinking this is related to the platform agent and not the RFC connection to SAP. What additional troublshooting steps can I take?
The OP Message created has the following
JCS-116012: Warning: Transient communication failure: Read timed out
Message Trace:
java.net.SocketTimeoutException: Read timed out
Stack Trace:
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.read(SocketInputStream.java:182)
at com.redwood.scheduler.infrastructure.net.HttpHeaders$LineInputStream.readLine(HttpHeaders.java:326)
at com.redwood.scheduler.infrastructure.net.HttpHeaders.parse(HttpHeaders.java:246)
at com.redwood.scheduler.infrastructure.net.RWHttpURLConnection.readResponse(RWHttpURLConnection.java:377)
at com.redwood.scheduler.infrastructure.net.RWHttpURLConnection.dispatch(RWHttpURLConnection.java:505)
at com.redwood.scheduler.infrastructure.net.RWHttpURLConnection.getInputStream(RWHttpURLConnection.java:366)
at com.redwood.scheduler.infrastructure.net.RWHttpURLConnection.getResponseCode(RWHttpURLConnection.java:251)
at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequest(PlatformAgentService.java:1527)
at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMessage(PlatformAgentReplyPoller.java:91)
at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(MessageEnabledWork.java:107)
at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.java:140)
at java.lang.Thread.run(Thread.java:722)