CA WA Agent and ESP: Jobs not running and ESP reports 'Transmitter Busy' or 'Agent notified'

Products

• ESP Workload Automation
• Workload Automation Agent
• CA Workload Automation DE - Business Agents (dSeries)

Issue/Introduction

ESP or CA Workload Automation DE report some job states as 'Agent Notified'. Jobs may continue to complete, but WA Agent is unable to notify scheduler about the state.  Scheduler or manager may not be able to submit new jobs to the agent.  Restarting the WA Agent may only help temporarily and jobs may again go in READY or Transmitter Busy state.

Environment

Release : Any

Component : CA ESP WORKLOAD AUTOMATION, CA WORKLOAD AUTOMATION DE (dSeries)

OS: Solaris, AIX, Linux

Cause

The WA Agent may not be able to properly communicate with the ESP / DE.  The issue is likely related to UNIX message queue.

Resolution

If a job shows any of these states 'Agent notified / Transmitter Busy' on the scheduler, then please do the following:

1.  Check to make sure the manager port is accessible from Agent machine.

Windows:  Run following command in Powershell

Test-NetConnection -ComputerName <manager_host> -Port <manager_port>

Test-NetConnection -ComputerName esp.example.com -Port 7005

Linux/UNIX

cat </dev/tcp/<manager_host>/<port>

cat </dev/tcp/deserver.example.com/7507

If port is accessible the command will just show a blank line.

2.  (Optional) Add a message queue

• Shutdown the agent.
• Navigate to agent install directory and remove rename database directory
• Navigate back to the agent install dir and create a file 'msgqueue' using touch command.
• Edit the agentparm.txt file and this line: oscomponent.msgqueue=/<path_agent_directory>/msgqueue
  
  • E.g oscomponent.msgqueue=opt/CA/WA_Agent/msgqueue
• Save the agentparm.txt and restart the agent
• Submit jobs and test

Note: The msgqueue file must be created in a directory which is accessible to agent and file should not be deleted. Do not create this file in /tmp directory.