-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All,
I was playing around with the manager webapp today and just for grins, I redeployed my webapp and then hit the "Find Leaks" button to see how long it would take Tomcat to decide that my webapp reloads cleanly. It didn't. That is, my webapp does not appear to cleanly reload. Which was a surprise to me. I waited a few moments and tried again: Find Leaks still says "there's a leak, confirm with a profiler". So I attached with YourKit, took a memory snapshot and started looking around: I found 4 WebappClassLoaders (1 for manager, 1 for my webapp, 1 for a dummy ROOT webapp I have and finally a started=false WebappClassLoader for the old pre-reload of my webapp). Interestingly, the started=false WebappClassLoader says that it is Weak/Soft Reachable. That means that tracing GC roots doesn't really work. Requesting GC via the manager changes nothing. Requesting GC via the profiler changes nothing. Does anyone have any good ideas for tracking-down what is keeping this WebappClassLoader in memory? Do I just have to intentionally exhaust the heap to convince the MM/GC that it should toss-out this WCL? Any suggestions would be greatly appreciated. Thanks, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCYHXYACgkQ9CaO5/Lv0PBOGwCguV4xkhvHZNGtpNEVy3nNUht0 X4cAoLB/OTKvHNMln2Jx3bfrK1TZ4PFo =D11z -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
