CA WA Agent For SAP: Jobs stuck or not running, memory issue

book

Article ID: 142411

calendar_today

Updated On:

Products

CA Workload Automation Agents CA Workload Automation Agent CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation AE - Business Agents (AutoSys)

Issue/Introduction

Jobs are submitted to WA SAP plugin.  are executing fine on SAP but not getting out of "SUBMIT" status in ESP

Cause

The agent logs may show error like these

------

12/XX/20XX 00:XX:26.788 UTC 1 SAPPlugin.Monitor:952125288025684548.CybThreadGroup.uncaughtException[:73] - Thread Monitor:123425288025123456[SAPPlugin] has had an uncaught exception
12/23/2019 11:24:26.789 EST-0500 1 SAPPlugin.Monitor:952125288025684548.CybThreadGroup.uncaughtException[:80] - java.lang.OutOfMemoryError: Java heap space
at java.lang.Throwable.getStackTraceElement(Unknown Source)
at java.lang.Throwable.getOurStackTrace(Throwable.java:827)
at java.lang.Throwable.printStackTrace(Throwable.java:656)
at java.lang.Throwable.printStackTrace(Throwable.java:643)

------

 

Environment

Release : 11.3/11.4/11.5

Component : CA WORKLOAD AUTOMATION AGENT 

Resolution

The OutOfMemoryError (OOM) message happened either because OS did not and/or could not give the additional memory to WA Agent.  Restart the agent and that will re-initiate the plugin.  If this is observed often then the following options is available:

1. Reduce the default heap size to 1 GB (or less) so agent doesn't ask for more memory than OS can give.  Use this parameter in agentparm.txt

oscomponent.jvm.x.options=-Xms128m;-Xmx1024m

Make sure that OS always has the max amount of memory (-Xmx) always free for the agent.  

Note: Agent will not take all the heap it is allowed (in above example, 1 GB).  It will take in small chunks from the OS.