Why does the CA Agent Technology (awservices) components spawn so many processes on Linux?

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• CA Unicenter NSM

Issue/Introduction

Description:

Your system has NSM agent technology running on a Linux Server. When reviewing the output of a "ps -ef" command, there are multiple processes for each of the agent technology component (i.e. awservices, aws_orb, aws_sadmin, caiLogA2, caiUxsA2).

Solution:

The NSM awservices (common services components) and agents are all multi-threaded. Unlike other UNIX platforms, Linux has different CPU scheduling for threads running in a process. For a multi-thread process on Linux, each thread has its own CPU scheduling, this is why we see multiple instances for awservices components in a PS output. It is normal to see multiple processes with the same name in Linux.

Many factors can effect how many "processes" are displayed by AT such as:

• The environment variable LD_ASSUME_KERNEL can affect this, as can LD_LIBRARY_PATH.
• The patch level of AT can also affect this.
• The patch level of the OS can also affect this.
• The resources the agents are configured to monitor.

Environment

Release: TNGEXO05500-11.2-Management-for Microsoft Exchange
Component: