search cancel

java.lang.OutOfMemoryError: Java heap space

book

Article ID: 8864

calendar_today

Updated On:

Products

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

Issue/Introduction

In some cases the Workload Automation Agent may report memory issues in logs. The following Exception maybe observed in  nohup.stderr located in AGENT_INSTALL_DIR.

  Exception in thread "Execution:6167018068990963554" java.lang.OutOfMemoryError: Java heap space
        at cybermation.plugins.sap.communicator.CybSAPResponse.getTableImage(Unknown Source)
        at cybermation.plugins.sap.communicator.CybSAPResponse.getTableImage(Unknown Source)
        at cybermation.plugins.sap.log.CybSAPLogAnalyzer.createSAPLog(Unknown Source)
        at cybermation.plugins.sap.log.CybSAPLogAnalyzer.createSAPLog(Unknown Source)
        at cybermation.plugins.sap.communicator.CybSAPJobManager.setJobLog(Unknown Source)
 ........

 

The Agent may shut down or service may be killed by OS.

Environment

Release: All Supported Versions
Component: Workload Automation Agent

Cause

The exception is due to the CA WA System Agent is running out of Java Virtual Machine allocated heap space. 

Resolution

Configure the heap using the "oscomponent.jvm.x.options" parameter in the agentparm.txt file.

oscomponent.jvm.x.options=-Xms<initial heap size>;-Xmx<maximum heap size> 
-Xms: Initial and minimum heap size.
-Xmx: Maximum heap size

Example

oscomponent.jvm.x.options=-XX:+UseGetTimeOfDay;-Xms256m;-Xmx512m

Make sure that OS always has the maximum heap size available.

Additional Information

Note: The memory allocation and usage can be seen in the simple_health_monitor.log file.