Support Article
Memory Pool Collection warnings at log file at Production
SA-32087
Summary
Memory Pool Collection warnings in log file and the system is very slow.
Error Messages
2016-12-23 10:12:05,458 GMT*7*PEGA0028*3940496384*3865470566*9bf59b41d4832165a0c253e12b37710c*NA*NA*NA*NA*NA*NA*NA*?
*-1*8969*Service
Thread*NA*com.pega.pegarules.management.internal.events.JVMNotificationManager*NA*NA*NA*NA*NA*NA*NA*NA*NA*NA*NA*NA*Collection
usage threshold exceeded for long-lived object memory pool (PS Old Gen) INFO:MemoryPool=PS Old Gen;PoolType=long-lived
object;Event=java.management.memory.collection.threshold.exceeded;TimeStamp=2016-12-23 10:12:05,451
GMT;Count=1;NotificationSequenceNo=1;Threshold=3865470566;Used=3940496384;Max=4294967296;Committed=4294967296;Init=4294967296;*
Steps to Reproduce
Restart the system.
Root Cause
The PEGA0028 alert is generated after the JVM has used garbage collection (GC) to reclaim memory from one of these memory pools, but the garbage collection failed to reduce the used memory.
Resolution
Tune the garbage collector referring the following PDN article:
https://pdn.pega.com/performance/understanding-the-pega0028-alert-gc-cannot-reclaim-memory-from-memory-pools
Published October 24, 2017 - 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.