Support Article
OutOfMemory Error taking the server down repeatedly
SA-20887
Summary
User reported that the Pega Rules Processor Commander(PRPC) dev environment is repeatedly down due to the OutOfMemory Error and creating multiple thread dumps and heap dumps.
Error Messages
2016-02-11 02:32:15,921 [ WebContainer : 3] [ STANDARD] [ ] [ HVE:01.01.01] (ssing.PegaGadget_Filter.Stream) ERROR 198.46.49.196|170.248.170.135 Seshagiri - Section 'pzPreProcessing' execution error on page '' of class 'PegaGadget-Filter'.
java.lang.OutOfMemoryError
:
native memory exhausted
at
java.lang.ClassLoader
.
defineClassImpl
(Native Method)
at
java.lang.ClassLoader
.
defineClass
(
ClassLoader.java
:
2
7
5
)
at
com.pega.pegarules.bootstrap.loader.PRAppLoader
.
findClassInternal
(
PRAppLoader.java
:
9
4
1
)
at
com.pega.pegarules.bootstrap.loader.PRAppLoader
.
findClass
(
PRAppLoader.java
:
4
5
9
)
at
com.pega.pegarules.bootstrap.loader.PRAppLoader
.
loadClass
(
PRAppLoader.java
:
7
6
1
)
at
com.pega.pegarules.bootstrap.loader.PRAppLoader
Steps to Reproduce
Not Applicable
Root Cause
The root cause of this problem is in a third-party defect as documented under IBM Websphere AS support doc -
https://www-304.ibm.com/support/docview.wss?uid=swg21660890
Resolution
The issue resolved after setting JVM Argument “-Xgc:preferredHeapBase=0x100000000” and user has not reported seeing the Native Memory /OOM exceptions.
Published March 18, 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.