Investigating OutOfMemoryError

The java.lang.OutOfMemoryError error is thrown when there is insufficient space to allocate an object in the Java heap (or a particular area of the heap). That is, the garbage collection cannot make any further space available for a new object and the heap cannot be expanded further. An OutOfMemoryError does not imply a memory leak – the issue can be as simple as a configuration issue where the specified heap size (or the default size if not specified) is insufficient for the application.

A good reference: http://help.sap.com/saphelp_nwesrce/helpdata/en/97/d0de42c02c420da92a7cec346f9168/content.htm

Make sure what type of OutOfMemoryError it is:

• Exception in thread “main” java.lang.OutOfMemoryError: Java heap space
• Exception in thread “main” java.lang.OutOfMemoryError: PermGen space
• Exception in thread “main” java.lang.OutOfMemoryError: Requested array size exceeds VM limit
• Exception in thread “main” java.lang.OutOfMemoryError: request bytes for . Out of swap space?

Other useful resources:

•  http://stackoverflow.com/questions/8966017/tomcat-outofmemoryerror-java-heap-space-24gb-system
• http://www.javaworld.com/article/2071737/core-java/plug-memory-leaks-in-enterprise-java-applications.html
• http://help.sap.com/saphelp_nwesrce/helpdata/en/97/d0de42c02c420da92a7cec346f9168/content.htm
•  http://www.techpaste.com/2012/07/29/steps-debugdiagnose-memory-memory-leaks-jvm/
• http://java.dzone.com/news/how-fix-memory-leaks-java