-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gary,
On 5/10/2011 3:55 PM, Gary Weaver wrote: > http://stufftohelpyouout.blogspot.com/2011/05/diagnosing-webappportlet-hot-deploy.html Generally speaking, when you have a permgen "leak" across webapp redeployments, this is the situation: 1. Webapp invokes some code that stores a reference to the webapp's WebappClassLoader 2. That reference is not cleared during undeploy [this is the leak] The big problem is that the WebappClassLoader keeps a reference to all java.lang.Class objects it loads, so it can be quite bulky when it leaks, depending on exactly how many classes your webapp has locally. markt has a great presentation which lays out the anatomy of these types of memory leaks, how to diagnose them, and often how to fix them. These are slides from a presentation at last year's ApacheCon NA. It's /very/ readable. http://people.apache.org/~markt/presentations/2010-11-04-Memory-Leaks-60mins.pdf - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3JmrQACgkQ9CaO5/Lv0PAwWwCfQNuuTZnw9JYqgVSdQ/daVABG 6jQAnRb1VJScgOjH8J73EKaWZLukKcqf =Bvw2 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
