On 25.04.2010 23:18, Sylvain Laurent wrote:
I don't understand what would be the purpose of this feature. Is it in order to really force a GC when clicking on the "Find leaks" button of the manager ?
Yes
If it's for that, I don't think it's worth the trouble. People really interested in fixing their leaking webapps should take a snapshot of the heap and analyze it to confirm (as advised by the manager page) and find the origin of the leak.
I'm not sure whether it's worth the trouble either. I just wanted to point out that actually there is a reliable way of triggering a full GC but not from within Java code.
The memory leak detection is not about finding the root cause - here you'll often need a heap dump - but a most likely reliable way of telling whether there is a webapp class loader related leak or not. That's where we need to force a GC.
Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
