https://issues.apache.org/bugzilla/show_bug.cgi?id=49395
--- Comment #3 from Konstantin Kolinko <knst.koli...@gmail.com> 2010-06-06 19:23:55 EDT --- Interesting, though there are some issues 1) Host.findReloadedContextMemoryLeaks is callable through JMX. I need to test it, but I suppose that ContextLeakInfo cannot be rendered by JConsole. 2) It looks like an API change for me. 3) I would like to see not only when the context was started, but also when it was stopped. 4) ContextLeakInfo.java needs the Apache license header. 5) i18n. 6) As a further enhancement I think that the result returned by StandardHost.findReloadedContextMemoryLeaks() might be sorted by contextPath and then by startDate. 7) The documentation has to be updated: manager-howto.xml, html-manager-howto.xml I think that the use cases for this improvement are the following: Knowing the times will allow someone to a) distinguish new results from the old ones, which is needed because the information on the leaked contexts accumulates over time. b) match the leaked application instance to a certain time frame in the deployment history of that web application, its logs, GC logs. E.g. if not each start/stop cycle exposes the leak, or if GC cannot be forced and we must wait some time before it occurs naturally. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
