Automic: ssh action pack jobs fail with "Could not create the Java Virtual Machine"

Products

• CA Automic Workload Automation - Automation Engine
• AUTOMIC WORKLOAD AUTOMATION
• CA Automic One Automation
• CA Automic Operations Manager
• CA Automic Oracle

Issue/Introduction

While executing many workflows/jobs using SSH Action Pack, some of them fail with the following error while launching ssh-tool.jar:

####################

20191204/101500.088 - U02001096 Job '1223685' uses client-wide resource '1:PCK.AUTOMIC_SSH.PRV.STORE/SSHTOOL' - 'C:\AE\Agents\Windows\Resources\0001\ssh-tool.jar'.

...

Error occurred during initialization of VM

Unable to allocate 131072KB bitmaps for parallel garbage collection for the requested 4194304KB heap.

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

"ERROR: ******** RUN COMMAND ACTION FAILED ********"

####################

 

 

Cause

System and Java configuration issue: insufficient memory to create a new JVM process.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

The error in the SSH job is related to a lack of memory while launching the job:
Unable to allocate 131072KB bitmaps for parallel garbage collection for the requested 4194304KB heap.
Error: Could not create the Java Virtual Machine.

It is due to the fact that the Java xms setting had been set to 4GB which is way too much for a simple ssh job.
Solution consists on adding to the Java startup settings a lower xmx / xms setting like 64MB for xms and 512MB for XMX.
JAVA_OPTS=-Xms64m -Xmx512m