Delete comment from: Java EE Support Patterns
Hi Anonymous,
What this feature simply does is thrown a preventive OOM before the actual JVM is in full hang & depletion status. It it thrown when it detects the JVM spends too much time in garbage collection.
In practice, it will only allows you to take some actions such as generating extra data points from your monitoring tool, thread dump etc.
If you are getting this error, it is a clear symptom that you are dealing with a Java Heap memory problem such as:
- Memory leak
- Sudden event / high memory thread consumers
- Improper Java Heap size tuning or GC policy etc.
I suggest my other post so you can actually see how the JVM native implementation is handling this logic.
http://javaeesupportpatterns.blogspot.com/2012/01/gc-overhead-limit-exceeded-understand.html
Regards,
P-H
Feb 6, 2013, 7:33:43 AM
Posted to GC overhead limit exceeded - Problem and analysis approach