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

java.lang.OutOfMemoryError: GC overhead limit exceeded



Server performance degrades and crashes with OutOfMemory error.

Error Messages

java.lang.OutOfMemoryError: GC overhead limit exceeded

Steps to Reproduce


Root Cause

After analyzing the Garbage Collection (GC) logs, 87.85% of GC time was caused by 'Metadata GC Threshold'. The threshold was set to 2 GB, which was not sufficient.


Perform the following local-change:

Tune the metaspace using below the below JVM argument.

-XX:MetaspaceSize=4 GB

This sets the size of the allocated class metadata space which triggers the GC the first time it is exceeded.


Published August 28, 2018 - 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