RA Agent fails to start with "error java.lang.OutOfMemoryError: Java heap space"
Article ID: 87615
Updated On:
Products
CA Automic Workload Automation - Automation Engine
AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction
Error Message :
java.lang.OutOfMemoryError: Java heap space
The RA Agent fails to start and the above error message is displayed in the agent's log file.
Note: This error may be seen on other RA Agents as well and is not specific to just the RA BusinessObjects Agent.
java.lang.OutOfMemoryError: Java heap space
The RA Agent fails to start and the above error message is displayed in the agent's log file.
Note: This error may be seen on other RA Agents as well and is not specific to just the RA BusinessObjects Agent.
Cause
Cause type:
Configuration
Root Cause: Not enough Heap Memory available to start the Java Virtual Machine
Configuration
Root Cause: Not enough Heap Memory available to start the Java Virtual Machine
Environment
Release: AOMBOA99000-3.0-Automic-Operations Manager-Business Objects Agent
Component:
Component:
Resolution
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.
Fix Status: No Fix
Fix Status: No Fix
Additional Information
Workaround :
In order to avoid this problem the maximum amount of memory available to the RA Agent should be increased. It is however also advisable to increase the minimum amount of memory in case the server is using a lot of memory otherwise the lack of memory at startup will remain undetected.In the documentation the recommended startup string is the following: java -jar -Xrs -Xmx256M ucxjcitx.jar disable_cache In cases where the agent doesn't start, it is recommended to increase the max memory available (Xmx) to 512M and also set the minimum to be available/reserved at startup (Xms) to 256M.In the example of RA.BusinessObject this gives the following in the Service Manger's smd-file: DEFINE RA-BO-Agent;/java/jre1.6.0_25/bin/java -jar -Xrs -Xms256M -Xmx512M /ra-core-bobj/ucxjcitx.jar -i/ra-core-bobj/ucxjcitx_bo.ini ;/ra-core-bobj
In order to avoid this problem the maximum amount of memory available to the RA Agent should be increased. It is however also advisable to increase the minimum amount of memory in case the server is using a lot of memory otherwise the lack of memory at startup will remain undetected.In the documentation the recommended startup string is the following: java -jar -Xrs -Xmx256M ucxjcitx.jar disable_cache In cases where the agent doesn't start, it is recommended to increase the max memory available (Xmx) to 512M and also set the minimum to be available/reserved at startup (Xms) to 256M.In the example of RA.BusinessObject this gives the following in the Service Manger's smd-file: DEFINE RA-BO-Agent;/java/jre1.6.0_25/bin/java -jar -Xrs -Xms256M -Xmx512M /ra-core-bobj/ucxjcitx.jar -i/ra-core-bobj/ucxjcitx_bo.ini ;/ra-core-bobj
Feedback
Powered by
