After googling a bit for error “java.lang.OutOfMemoryError: PermGen space” I found many sites talking about that problem. Some tried passing command line arguments to the JVM or changing the size of the PermGen space, others end up recommending using a VM from BEA or IBM, all without success.
But after a closer look at their comments I ended up at Frank Kieviet blog.
Frank explains what really is a PermGen error
The problem in a nutshell
Application servers such as Glassfish allow you to write an application (.ear, .war, etc) and deploy this application with other applications on this application server. Should you feel the need to make a change to your application, you can simply make the change in your source code, compile the source, and redeploy the application without affecting the other still running applications in the application server: you don’t need to restart the application server. This mechanism works fine on Glassfish and other application servers (e.g. Java CAPS Integration Server).
The way that this works is that each application is loaded using its own Classloader. Simply put, a Classloader is a special class that loads
.class files from jar files. When you undeploy the application, the Classloader is discarded and it and all the classes that it loaded, should be garbage collected sooner or later.
Somehow, something may hold on to the Classloader however, and prevent it from being garbage collected. And that’s what’s causing the
java.lang.OutOfMemoryError: PermGen space exception.
PermGen space anyways? The memory in the Virtual Machine is divided into a number of regions. One of these regions is
PermGen. It’s an area of memory that is used to (among other things) load class files. The size of this memory region is fixed, i.e. it does not change when the VM is running. You can specify the size of this region with a commandline switch:
-XX:MaxPermSize. The default is 64 Mb on the Sun VMs.
If there’s a problem with garbage collecting classes and if you keep loading new classes, the VM will run out of space in that memory region, even if there’s plenty of memory available on the heap. Setting the
-Xmx parameter will not help: this parameter only specifies the size of the total heap and does not affect the size of the
… and how to use new profiling tools in Java 6 to fix Classloader leaks.
Resuming, the steps are:
- start your application server
- deploy and run your application
- undeploy the application that is leaking (just the application not the server)
- trigger a memory dump
jmap -dump:format=b,file=leak <PID>
- run jhat (with modification, Java SE SDK 6.0 update 1 has the updated code)
jhat -J-Xmx512m leak
- go to jhat report http://localhost:7000/ (http://localhost:7000/oql/ if you need the OQL (Object Query Language))
- find a leaked class (any class of your application since you shouldn’t see any objects of the classes that you deployed)
- locate the Classloader
- find the “Reference chains from root set”
- inspect the chains, locate the accidental reference, and fix the code
Some try even to go further on finding Orphaned Classloaders others try to nicely present the leaking classes in a form of a HTML table histogram.
These tools can really help, use them!