Process Automation: 2 agents and process instances using the one agent are not completing. Returns java.net.SocketTimeoutException: Read timed out in the c2o.log.

Document ID : KB000011739
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Everything was working properly but now Process Instances which use 1 of 2 agents are failing.

WARN [com.optinuity.c2o.transport.Client] IO Error while sending message -
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:166)

Both agents show as active in the orchestrator.

Question:

Why does my agent show as active but not running properly anymore?

Environment:
This is not environment specific. This can happen on a single node or a cluster.
Answer:

If your agents show as Active in the Orchestrator UI please review the network connection. 

 

Troubleshooting:

1.  Ping from the orchestrator system to the agent system.  Does it work?

2.  Run:

netstat -an | find "7003"

Does the orchestrator have access to that port?

Process Automation requires the ability to talk between all the servers, including agent servers, directly without the load balancer.

 

 

Additional Information:

Continue to work with your network team to allow communication on port 7003.  Please also check your anti-virus software.  After some system patches it is possible for Anti-virus to block or not allow communication on port 7003.  Once this is corrected, process instances using agents will begin to run properly again.