On Thu, Jun 25, 2009 at 2:52 PM, Jacob Kessler<
Jacob.Kessler@...> wrote:
> Yes. By default, the HotSpot JVM doesn't bother garbage collecting the
> permanent generation at all, since it's assumed that very few classloaders
> will become collectible. Since each application gets its own classloader,
> application servers are an obvious exception to this. You'll want to run
> with the following JVM options:
>
> -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled
>
> Which will enable class unloading.
For the record, here's the JVM option recipe that I ended up using :
-XX:MaxTenuringThreshold=15
-XX:MaxNewSize=512m
-XX:NewSize=512m
-Xverify:none
-XX:+UseConcMarkSweepGC
-XX:ParallelGCThreads=4
-XX:+UseParNewGC
-XX:+CMSClassUnloadingEnabled
-Xmx2100m
-Xms2100m
-Xss1m
-XX:MaxPermSize=512m
-server
-XX:NewRatio=1
After implementing these set of options and giving Grizzly a chance to
release it's held resources I am still seeing runtimes held onto after
a reload.
-Chad J
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
