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

JVM heap issue crashing the JVMS



Heap dump was collected from Production node and inspected through a heap analyzer. The report suggests that there might still be a minor memory leak. A particular object was found holding 11% of the total heap at the time of collection of heap dump.  This collection consisted of over 24,000 instances of PRPC class  LockManagerImpl$LockInformation

Error Messages

Not applicable.

Steps to Reproduce

Occurs during normal system use - no reproduction scenario.

Root Cause

Pegasystems defect identified - leaking instances of  LockManagerImpl$LockInformation class were not getting cleared from memory.


Install hotfix HFix-30363, which will allow the SystemCleaner agent to remove expired locks from memory (as it was already removing them from the database table pr_sys_locks).
Suggest Edit

Published December 15, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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