Java/Groovy jobs failing with OutofMemoryError

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Java/Groovy jobs failing with OutofMemoryError

Environment

Release: 8.x, 9.x

Resolution

Symptoms  

The Applications Manager java processes are running fine but certain Java/Groovy jobs are failing with out of memory errors. For these jobs the following error is observed in the AM output files:

JVMDUMP006I Processing Dump Event "systhrow", detail "java/lang/OutOfMemoryError" - Please Wait.

JVMDUMP007I JVM Requesting Snap Dump using '/home/appworx/run/Snap.20130311.091528.18939918.0001.trc'

JVMDUMP010I Snap Dump written to /home/appworx/run/Snap.20130311.091528.18939918.0001.trc

JVMDUMP007I JVM Requesting Heap Dump using '/home/appworx/run/heapdump.20130311.091528.18939918.0002.phd'

JVMDUMP010I Heap Dump written to /home/appworx/run/heapdump.20130311.091528.18939918.0002.phd

JVMDUMP007I JVM Requesting Java Dump using '/home/appworx/run/javacore.20130311.091528.18939918.0003.txt'

JVMDUMP010I Java Dump written to /home/appworx/run/javacore.20130311.091528.18939918.0003.txt

JVMDUMP013I Processed Dump Event "systhrow", detail "java/lang/OutOfMemoryError".

Caught: java.lang.OutOfMemoryError

 at runube.run(runube.groovy:158)

---

Cause

The java process specific to the job is running out of memory and core-dumping. This causes the job to fail as well.

---

Resolution

Increasing the java -Xmx argument for the JVM which is specific to the groovy or java job/program (depending on what is being run) should resolve the issue.