Clarity - error java.lang.OutOfMemoryError: GC overhead limit exceeded

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Clarity is not accessible, slow or services crash with java.lang.OutOfMemoryError: GC overhead limit exceeded 

Environment

All Supported Clarity Releases

Cause

GC handling is not optimal

• Excessive GC Time leads to OutOfMemoryError
• The java.lang.OutOfMemoryError: GC overhead limit exceeded error with the G1 garbage collector (G1GC) means the JVM is spending over 98% of its CPU time on garbage collection but is reclaiming less than 2% of the heap, effectively making little progress.

Resolution

1. Review the JVM settings of the application in properties.xml, specifically in regards of Garbage collection (GC)
2. Increase java heap size if required
3. Adjust the GC settings accordingly to allow for better GC handling to avoid excessive GC time
4. Settings to review and consider among others, based on Oracle Documentation : 
   • -XX:-UseGCOverheadLimit 
   • -XX:MaxGCPauseMillis
   • -XX:+UseG1GC

• We recommend reviewing the official Oracle recommendations and tuning the settings to align with your specific environment