Support Article

Memory leak and CPU spike in Pega 7.1.8 application



A systems administrator frequently observes out of memory errors reported by the Java Virtual Machine (JVM).  

As a result, the system destabilizes, and the business complains of lost productivity or low performance.

Error Messages

No error messages are displayed on screen.  However, the following error is observed multiple times in the Pega Logfile:

2016-10-24 10:49:32,640 [ES PassivationDaemon] [  STANDARD] [                    ] [                    ] (ternal.async.PassivationDaemon) ERROR   - Failed to process passivation queue: 

Java heap space
(Native Method)

Also, the ALERT log contains numerous PEGA0028 ALERTs.

Steps to Reproduce

Unknown. No specific steps were identified to reproduce this issue.

Root Cause

The Java.lang.outofmemoryerror is reported as a NATIVE error condition, which means that this is an internal problem with the JVM and its interaction with operating system, as opposed to the JVM attempting to obtain more memory from its designated heap.

This error condition is a known old problem in 1.6 IBM JVM J9 releases.


To resolve this issue, update the existing JVM to the latest release.

Published November 10, 2016 - Updated December 15, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.