WA Agent Ports remain into CLOSE_WAIT status

Products

• CA Workload Automation DE - Business Agents (dSeries)
• CA Workload Automation DE
• DSERIES- SERVER
• CA Workload Automation DE - System Agent (dSeries)
• CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

The WA Agent port (7507) stays in CLOSE_WAIT status and not ESTABLISHED for all the agent connections.

Environment

Release : ANY

Component : CA WORKLOAD AUTOMATION DE (DSERIES), CA WORKLOAD AUTOMATION WA AGENT

OS: Linux

Cause

The CLOSE_WAIT state may sometimes not get cleared by the kernel.  This can result in performance issues.  The following may be seen by running command: ss -ntp4
 

State           Recv-Q Send-Q   Local Address:Port   Peer Address:Port 

CLOSE_WAIT       0      0       10.10.10.1:22        10.10.20.2:60905  users:(("sshd",pid=xxxx,fd=3)

CLOSE_WAIT       0      0       10.10.10.1:9997      users:(("splunkd",pid=xxxx,fd=52))

CLOSE_WAIT      74      0       10.10.10.1:5222      users:(("osad",pid=xxxx,fd=3))

CLOSE_WAIT       0      0       10.10.10.1:389       users:(("sssd_be",pid=xxx,fd=21))

Resolution

If several other process other than WA Agent are also stuck in CLOSE_WAIT then consult System Administrator on upgrading the OS and kernel.
Some older RHEL and OEL kernels (3.10.x) have been observed to have issues with CLOSE_WAIT.