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.
Steps to Reproduce
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.
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.