Troubleshooting
Problem
Troubleshooting tips for out-of memory error from purge agents
Symptom
Troubleshooting tips for out-of memory error from purge agents.
Error MessageOut of Memory error thrown by agent JVM resulting in agent server crash
Caused by: java.lang.OutOfMemoryError: Java heap space
at com.yantra.integration.adapter.IntegrationAdapter.onMessage(IntegrationAdapter.java:330)
Yantra encountered Java Virtual Machine Error at 2009-04-18 16:21:11.568 , verify your JVM settings......
Halting the system................
Yantra encountered Java Virtual Machine Error at 2009-04-18 16:21:11.568 , verify your JVM settings......
Halting the system................
Resolving The Problem
Whenever the agent that is executing purge throws out-of memory, use the following steps to troubleshoot the same.
1. As a first step, check the JVM memory parameters (-Xmx, -Xms, etc).
If the maximum allocated memory is very low, (-Xmx=128m or 256m), there are possible out-of memory issues. In such cases, increase the agent JVM memory to either 512m or 1024m in the worst case. This is still dependent on the architecture of the machine though.
If the maximum allocated memory is very low, (-Xmx=128m or 256m), there are possible out-of memory issues. In such cases, increase the agent JVM memory to either 512m or 1024m in the worst case. This is still dependent on the architecture of the machine though.
2. If maximum required memory is allocated and the agent still throws an OOM, following purge criteria can be checked:
a. Check whether the purge agent is in 'Test Mode' or in 'Live Mode'.
Running the purge agent in Test mode with test data will not cause any issues.
Running the purge agent in Test mode with test data will not cause any issues.
b. If the purge agent is run in Test mode with production (huge) data, it can potentially cause OOM, due to the below reason:
i. In Test Mode, system will not remove any record from the table; instead, it will form an output for all the purge-ready records.
ii. If the records are too huge, the system will try to form a huge XML for all the purge-ready records and can result in OOM.
c. In Live mode, system directly does the DELETE from the database table and does not form any outputs.
Hence, Sterling recommends executing purge agents in Test Mode with a reasonably low volume of data.
[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Historical Number
NFX6189
Product Synonym
[<p><b>]Severity[</b><p>];Normal
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21558637