On 5/10/11 8:55 PM, Gary Weaver wrote: > Here's what I did and what little I came up with: > http://stufftohelpyouout.blogspot.com/2011/05/diagnosing-webappportlet-hot-deploy.html > > I'm definitely not an expert at diagnosing leaks, so if you have any > recommendations/comments, please let me know. > > I unfortunately started off just thinking I could tune JVM settings, not > just by bumping up permgen but by adding things like: > > -XX:+UseParNewGC > -XX:+UseConcMarkSweepGC > -XX:+CMSPermGenSweepingEnabled > -XX:+CMSClassUnloadingEnabled > > But, I was (really) wrong as you can see in the post, along with the various > tools used to try to identify what was causing the issue(s). > > It doesn't seem like determining exactly what is leaking memory (at least in > the case of permgen and hot-redeploys/hot-deploys) is a whole lot easier > than it was years ago, unless I'm doing something wrong, which I most likely > am. Thanks in advance for any feedback! > > Gary >
Did you examine the Tomcat 7 logs during redeploy cycles? VisualVM can also take and/or open a heap dump. p
signature.asc
Description: OpenPGP digital signature
