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

Heap usage doubling when observing PEGA0046 alerts



PRPC cancels the loading of the data page by the background requestor and instead loads it in the foreground, and simultaneously writes out a PEGA0046 alert to the PegaRULES-ALERT.logs, but doesn't remove the memory from the heap for the Asynchronous Data Pages which are pulled to the foreground processing.

Sharp increase in heap usage, shortly followed by Out of Memory alerts when the heap is fully utilized.

Garbage collection is taking place, but not regularly enough to support this change.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

A defect in Pegasystems’ code or rules: While queuing the data page batch task in etier, task gets add to mBatchRequestorCollection but while removing a code left over from some cleanup in Garbage Alerts in method AsyncServiceBatchTask.removeBatchRequestorTask(), which means these tasks are not cleaned up.

Hence a leak.


Apply HFix-35902.

Published November 2, 2017 - 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