tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 49395] manager.findLeaks : display the date when the leaking context was started
Date Sun, 06 Jun 2010 23:23:58 GMT

--- Comment #3 from Konstantin Kolinko <> 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

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) 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,

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

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:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message