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

--- Comment #15 from Henning Blohm <henning.bl...@gmail.com> 2010-10-07 
10:41:50 EDT ---
(In reply to comment #14)
> The standard LogManager can't be used with Tomcat. If it is used, then a range
> of problems will occur including logger mix-ups and memory leaks. The
> expectation is that JULI's LogManager is used.
> 
> The assumption is that in the rare scenarios where it is safe to use the
> standard LogManager (and I suspect there are very, very few of these) they
> would be embedded scenarios where clearReferencesLogFactoryRelease could be 
> set
> this directly on the class loader. In a standard Tomcat install setting this
> option will cause nothing but problems.
> 
> The property could be exposed on the Context but I'm reluctant to expose an
> option that has no upside. If there was a valid use case for setting this in a
> standard Tomcat install then an enhancement request to that effect would be
> considered but right now I don't see a valid use case.

Mark, 

your comments on this issue are truely irritating. There are people that really
want to use the standard log manager. I want to. Registering application level
log handlers is the exception. Let people handle it.

The way it is handled now breaks the use of the standard LogManager - which is
none of Tomcat's business. We will certainly not make JULI the underpinning of
our infrastructure (that could - but as it stands will not - embed Tomcat) just
because you don't like the standard LogManager.

Those mixups and memory leaks are mostly insignifcant to the development
scenario and much less so in production scenarios - supposing you hit the
problem at all. Imposing JULI on the world just to be right is not reasonable.

Henning

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

Reply via email to