cybAgent.bin and virtual memory

Products

• Workload Automation Agent
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

I'm trying to better understand the virtual memory consumption by the cybAgent.bin process. We have 2 servers which have identical OS's and on one server, the cybAgent process is using 507MB of virtual memory and on the other server it's using 6.4GB of virtual memory.

Environment

Release: All Supported Versions
Component: Workload Automation Agent

Cause

The Agent is actually not using 6.4GB of virtual memory but Java is reserving the maximum heap from virtual memory space. The maximum allocateable memory is based on the available resources on the server so java can reserve the virtual memory differently on each server and Operating System.

Resolution

You can limit the maximum allocateable java virtual memory for the agent using the following parameter;
oscomponent.jvm.x.options=-Xmx<size>
Where -Xmx<size> is the maximum heap size.

On the other server with 6.4GB of virtual memory, you can configure the agent to use up to 512MB of java memory for heap by adding the parameter to the agent's agentparm.txt file. For example;

oscomponent.jvm.x.options=-Xmx512m

The value could be increased as needed if the resources is available on the agent computer.

You need to restart the agent for the change to be effected. The simple_health_monitor.log in agent's log directory will show the maximum allocateable and total allocated heap of memory for the agent.

Additional Information

Make sure agent's log.level is set to 5 or greater, and core.health.monitor.enable parameter set to true in agentparm.txt to log the memory usage in simple_health_monitor.log.