Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Some nodes crash and require restart



2 nodes out of 13 became unresponsive and required rebooting. After rebooting, they function as expected.

Error Messages

OutOfMemoryError occurring within PassivationDaemon:

####<Dec 12, 2014 10:26:40 AM CST> <Notice> <Stdout> <holder_xxxx> <ManagedServer_5> <Dispatcher-Thread-22> <<WLS Kernel>> <> <> <1418401600248> <BEA-000000> <2014-12-12 10:26:40,237 [ES PassivationDaemon] [  STANDARD] [                    ] (ternal.async.PassivationDaemon) ERROR   - Failed to process passivation queue: 
java.lang.OutOfMemoryError: Java heap space
    at com.pega.pegarules.priv.factory.ByteArrayFactory.newProduct(
    at com.pega.pegarules.priv.factory.AbstractContainerFactory.acquireObject(
    at com.pega.pegarules.priv.factory.ByteArrayFactory.acquire(
    at com.pega.pegarules.session.internal.mgmt.base.ThreadPassivation.getPageBytes(
    at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.getPageBytes(
    at com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage.passivatePage(
    at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.savePage(
    at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.processPassivationQueue(
    at com.pega.pegarules.session.internal.async.PassivationDaemon.processPassivationQueue(

Steps to Reproduce


Root Cause

Inspection of ALERT logs show a customer process which consumes over 1.5GB of heap space - this is an iterative process that attempts to perform a bulk operation and utilizes all available heap.


The root cause of this problem is a defect in customer application code/rules.

Sent feedback and ALERT excerpts which outline the application process that is consuming large (1.5GB amounts of heap).  When the user responsible for this process goes idle (while the large data is still in their clipboard), the passivation daemon attempts to store their requestor data which then puts the JVM OutOfMemory.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us