ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

java.net.SocketTimeoutException: Read timed out

book

Article ID: 222636

calendar_today

Updated On:

Products

Workload Automation Agent

Issue/Introduction

ESP Servers shows agent is notified. But the Agent doesn't show any logs on our client machine.

Agent version is :

CA Workload Automation Agent for: Linux x86_64 64-bit
11.4, Service Pack 01, Maintenance Level 0, Build 1933

 

 

 

 

Environment

Release : 11.4

Component : CA Workload Automation System Agent

Resolution

Common error "java.net.SocketTimeoutException: Read timed out" in the receiver log. 

08/13/2021 14:18:38.721-0400 2 TCP/IP Controller Plugin.Receiver pool thread <Slow:1>.CybReceiverChannel.a[:158] - Conversation from <IP_MASKED>:5778 to <IP_MASKED>:3521 arrived
08/13/2021 14:18:49.782-0400 1 TCP/IP Controller Plugin.Receiver pool thread <Slow:1>.CybReceiverChannel.a[:234] - cybermation.library.communications.CybConversationTimeoutException: Read timed out
                                                                                                                    at cybermation.library.communications.protocol.CybCommunicationProtocolDynamic.a(CybCommunicationProtocolDynamic.java:680)
                                                                                                                    at cybermation.library.communications.protocol.CybCommunicationProtocolDynamic.receiveMessage(CybCommunicationProtocolDynamic.java:362)
                                                                                                                    at cybermation.library.communications.CybConversation.receiveMessage(CybConversation.java:458)
                                                                                                                    at cybermation.commplugins.tcpip.receiver.CybReceiverChannel.a(CybReceiverChannel.java:174)
                                                                                                                    at cybermation.commplugins.tcpip.receiver.CybReceiverChannel.call(CybReceiverChannel.java:139)
                                                                                                                    at cybermation.commplugins.tcpip.receiver.CybReceiverChannel.call(CybReceiverChannel.java:51)
                                                                                                                    at cybermation.commplugins.tcpip.receiver.CybReceiverScheduler$CallableWrapper.call(CybReceiverScheduler.java:353)
                                                                                                                    at cybermation.commplugins.tcpip.receiver.CybReceiverScheduler$CallableWrapper.call(CybReceiverScheduler.java:317)
                                                                                                                    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
                                                                                                                    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                                                                                                                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                                                                                                                    at java.lang.Thread.run(Thread.java:748)
                                                                                                                   Caused by: java.net.SocketTimeoutException: Read timed out

This type of error is generally network related. While this Communities Discussion talks about network communications to a VIP for a cluster configuration, the content still applies with respect to network communications.

You indicated in response to my questions that the port is open on firewall to allow communications. According to the agentparm configuration you use port 3521 for agent and scheduler port communications.

As this error is typically network related, confirm that port 3521 is opened bi-directionally on your firewall. 

  • From your Linux agent server: nc -zv <manager host name> 3521
  • From Mainframe server: telnet <agent host name> 3521