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.

Reconnection of Unix Agent version 12.0.1+hf.4.build.1477 fails, resulting in looping Agent

book

Article ID: 88168

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
MAIN-THREAD 20170413/191804.126 ReadSelectAll Wrong select for socket : 11, error : 'Connection refused'

The issue described in this article only affects Unix Agent version 12.0.1+hf.4.build.1477.

The Agent works as expected and there is no impact to the system under regular circumstances. However, in cases where the TCP/IP connection between the Agent and the Communication Process (CP) is interrupted, the reconnect may fail.
 
During normal operations when there is an Agent reconnect the Agent will connect to all CPs specified in the INI file (cp= entry in tcp/ip section and entries from CP_LIST section). In case one of the listed CPs is unavailable, the Agent receives an error (connection refused), which is ok as long as you have at least one CP available.
 

Example:

MAIN-THREAD      20170413/191804.126 ReadSelectAll     Wrong select for socket : 11, error : 'Connection refused'
MAIN-THREAD      20170413/191804.126 ReadSelectAll     Wrong select for socket : 12, error : 'Connection refused'
MAIN-THREAD      20170413/191804.126 ReadSelectAll     Wrong select for socket : 13, error : 'Connection refused'
MAIN-THREAD      20170413/191804.126 ReadSelectAll     Wrong select for socket : 14, error : 'Connection refused'
MAIN-THREAD      20170413/191804.126 ReadSelectAll     Wrong select for socket : 15, error : 'Connection refused'
MAIN-THREAD      20170413/191804.126 ReadSelectAll     Wrong select for socket : 16, error : 'Connection refused'
 
However, in the Unix Agent version 12.0.1+hf.4.build.1477 this scenario is not handled normally.  Instead, the socket remains active and will not be closed and removed which may cause the Agent to loop endlessly.

 

Cause

Cause type:
Defect
Root Cause: Unix Agent version 12.0.1+hf.4.build.1477 sometimes leaves sockets active that should be closed and removed which can cause the Agent to get in an endless loop.

Environment

OS: Unix
OS Version: N/A

Resolution

Update to a fix version listed below or a newer version if available.



Fix Status: Released

Fix Version(s):
Component(s): Agent Unix

Automation Engine 12.0.1 HF5 - Available

Additional Information

Workaround :
N/A