search cancel

Could not reserve enough space for object heap error when starting java agents

book

Article ID: 87178

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

When attempting to start a java agent like SAP, Peoplesoft, RA agents (RA FTP, RA WebServices, etc...), etc...

the following message occurs on the command line standard out:

Error occurred during initialization of VM
Could not reserve enough space for object heap

OR

Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap

This error is only seen when starting the agent from the command line. The service manager fails to start the agent with error 'No associated window can be found' with a exit code as 1.

The only way to identify this error is to start the agent from the command line.

Environment

OS: Windows
Agent: Any Java based agent (started with a .jar file)

Cause

This is by design - Additional RAM is needed for the Java VM.

Resolution

This error indicates the system does not have enough RAM to allocate to the Java virtual machine. The best long term solution is to add more RAM to the system. 

It is possible to start the agent with less memory allocated using a lower number for the -Xmx[number]m start parameter.  In the second example above, -Xmx1024m works correctly while -Xmx2048m throws the error.

While -Xmx1024 can be used in the example above, allocating just 1 GB of memory to the agent, at some point the agent may need to use more memory and will crash if it runs out of allocated memory.

The documentation here: https://docs.automic.com/documentation/WEBHELP/English/all/components/DOCU/21.0.4/Automic%20Automation%20Guides/Content/Installation_Common/install_Sizing_QandA.htm#link3

states that "An average used java agent will need between 512-1024 MB, but in some cases this may be more." 

Broadcom's recommendation would be to add memory to the server so that this agent can have 2G allocated to it now instead of running into problems with not enough memory in the future.

Additional Information

Workaround :
Restarting the Windows box may free up enough RAM to work around this issue.

Attachments