Support Article
OutOfMemory errors
SA-2364
Summary
A couple of Instances of OOMErrors were observed in Production logs in August and September. Root cause analysis of the same is expected.
More users were added recently. Approximately 500 users were online when the OOMErrors were observed.
Error Messages
2014-09-04 12:28:04,043 [ WebContainer : 15] [ ] [ ] ( web.impl.WebStandardImpl) ERROR - null: Unhandled error in ETier invocation
java.lang.OutOfMemoryError
2014-09-08 15:26:30,637 [ WebContainer : 29] [ ] [ ] (ngineinterface.service.HttpAPI) ERROR pega.fg.rbc.com|10.208.79.5 - 10.208.79.5: java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
2014-09-08 15:26:30,637 [ WebContainer : 29] [ ] [ ] (ngineinterface.service.HttpAPI) ERROR pega.fg.rbc.com|10.208.79.5 - 10.208.79.5: java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
Steps to Reproduce
NA
Root Cause
Application Memory usage trend analysis from the PegaRULES log over 24 hour periods indicate that the Average Heap usage was ~5.5 GB out of 6 GB (max). The above pattern indicates high heap memory usage by the application under steady load and normal business operations over a period of time and not because of any single system / user activity. Also the above indicates that the application has a genuine need for additional heap memory considering the recently added user load.
Resolution
The following are recommendations / links from IBM to tune the JVM Heap size –
Size your Java heap so that your application runs with a minimum heap usage of 40%, and a maximum heap usage of 70%.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.