https://issues.apache.org/bugzilla/show_bug.cgi?id=52850
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #8 from Mark Thomas <ma...@apache.org> 2012-03-19 19:12:45 UTC ---
I've been looking at this some more.
The test cases don't do what they are meant to because they don't trigger a
leak because the web application class loader isn't used to load the servlets
and associated classes. That is almost certainly why you incorrectly thought
you needed to rework loadedByThisOrChild.
I have re-worked the tests and direct leaks are now being created and detected
as intended.
Indirect leaks appear to be being generated (although I need to double check
that it is the intended leak rather than some other leak) but are not yet being
logged. Work continues.
I have also have found and fixed a JMX related memory leak.
--
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
