https://issues.apache.org/bugzilla/show_bug.cgi?id=48716
--- Comment #16 from S. Ali Tokmen <postmas...@alishomepage.com> 2010-10-07
14:27:23 EDT ---
(In reply to comment #15)
> Imposing JULI on the world just to be right is not reasonable.
I cannot agree more. Tomcat, as a Java application like any other, should NOT
be imposing a logger but rather reuse the existing logger.
(Bis repetita) The correct implementation for this memory leak avoiding
mechanism would, I guess, look like that:
To clean up all of the current Web application's loggers:
get all loggers' names
for each logger
get all handlers
for each handler
if the handler's class can be loaded using the WebAppClassLoader
AND cannot be loaded using the WebAppClassLoader's parent
then
remove this handler
else don't touch
// that logger belongs to some other application
// or to Tomcat itself
--
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
