Support Article
Native memory gets exhausted in Pega 7.1.7
SA-11128
Summary
When running Pega 7.1.7 on WebSphere Application Server (WAS) 7.0.0.33 and Oracle DB 12c on Linux 2.6.32-504.8.1.el6.x86_64 using Java 1.6.0, user receives as many Native Memory Exhausted errors in the logs of development in multiple nodes system.
Error Messages
2015-06-04 02:40:55,084 [ WebContainer : 4] [TABTHREAD0] [ ] [APP:01.01.01] (il.classloader.PRClassLoaderDB) ERROR server|<IP> user - (com.pega.pegarules.exec.internal.util.classloader.PRClassLoaderDB$Loader@52245224) Error in defineClass: com.pegarules.generated.html_section.ra_stream_productselection_6b2e0799a21e719a14115d99f78b7389
java.lang.OutOfMemoryError
:
native memory exhausted
at
java.lang.ClassLoader
Steps to Reproduce
Run Pega <fta>PRPC</fta> 7.1.7 on WAS 7 Fix Pack 33 and logical Oracle DB 12c.
Root Cause
The root cause of this problem is defect or misconfiguration in the operating environment. The native memory was being used up.
Resolution
This issue is resolved through the following local-change:
Add the following JVM setting -Xgc:preferredHeapBase=0x100000000 to start the Heap at the 4GB mark.
Published November 17, 2015 - 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.