OutOfMemoryError - GC overhead limit exceeded
Someone asked me recently about the following exception on their ColdFusion server:
java.lang.OutOfMemoryError: GC overhead limit exceeded
This exception is thrown by the garbage collector (in the underlying jvm, it's not specific to ColdFusion), when it is spending way too much time collecting garbage. This error essentially means that you need to add more memory, or reconfigure your garbage collection arguments. You can suppress this error by adding
-XX:-UseGCOverheadLimit to your JVM startup arguments.
Here's what Sun has to say about it:
The parallel / concurrent collector will throw an
OutOfMemoryErrorif too much time is being spent in garbage collection: if more than 98% of the total time is spent in garbage collection and less than 2% of the heap is recovered, an OutOfMemoryError will be thrown. This feature is designed to prevent applications from running for an extended period of time while making little or no progress because the heap is too small. If necessary, this feature can be disabled by adding the option
-XX:-UseGCOverheadLimitto the command line.
Like this? Follow me ↯Tweet Follow @pfreitag
OutOfMemoryError - GC overhead limit exceeded was first published on March 25, 2010.
If you like reading about java, jvm, coldfusion, garbage, collector, tuning, or performance then you might also like:
- Updating Java on ColdFusion or Lucee
- Getting Size of Heap and Non Heap Memory in CFML
- Adobe Says Go Ahead and Upgrade your ColdFusion JVM
- Java Performance Tuning Guide
- ColdFusion Garbage
- Tuning Garbage Collection
- Enabling Unlimited Strength Cryptography in ColdFusion
- HashDOS and ColdFusion