[Bug 56275] Classloader leak in DirContextURLStreamHandler

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=56275

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
Hmm. For this to happen an exception would have to be thrown during web
application stop that prevented the code that de-registers the associated class
loader from being called.

8.0.x is immune to this issue because the registration and deregistration code
has been removed as part of the refactoring of resource handling.

I've been through the 7.0.x code and I can't see any obvious way to trigger
this. All the obvious exceptions that could trigger the problem are caught,
logged and not re-thrown. The only exceptions excluded from the process are
fatal to the JVM anyway.


I do see a possible way to trigger this memory leak in 6.0.x but I need to do
some testing to confirm it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org