java.lang.OutOfMemoryError: GC overhead limit exceeded & java.lang.OutOfMemoryError: Java heap space

Issue –> When starting the  SOA managed server we will encounter these errors.

Error –>

java.lang.OutOfMemoryError: GC overhead limit exceeded

Solution –>

According to Sun, the error happens “if 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.”.

Apparently, one could use the command line to pass arguments to the JVM for

  • Increasing the heap size, via “-Xmx1024m” (or more), or
  • Disabling the error check altogether, via “-XX:-UseGCOverheadLimit”.

The first approach works fine, the second ends up in another java.lang.OutOfMemoryError, this time about the heap.

For out of memory error you need increase the xms parameteres.

Error–>

java.lang.OutOfMemoryError: Java heap space

Solution –>

The size of those regions is set during the Java Virtual Machine (JVM) launch and can be customized by specifying JVM parameters -Xmx and -XX:MaxPermSize. If you do not explicitly set the sizes, platform-specific defaults will be used.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s