You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2010/02/10 10:43:43 UTC

DO NOT REPLY [Bug 48716] Embedded Tomcat JULI aggressively resetting default logging configuration

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

--- Comment #1 from Mark Thomas <ma...@apache.org> 2010-02-10 01:43:42 UTC ---
If you use the standard LogManager then you are going to get memory leaks. You
need to be using JULI or another LogManager implementation that is class loader
aware.

If this call is only used with JULI then other class loader aware LogManager
implementations will have no opportunity to clean up.

On the basis that there may be some valid embedded use cases where you do need
to disable the call to reset(), then a better approach is probably to make this
configurable, with the default that the call takes place.

-- 
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org