tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39296] - Misuse of Commons Logging
Date Thu, 13 Apr 2006 10:03:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39296>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39296





------- Additional Comments From skitching@apache.org  2006-04-13 11:03 -------
Well, deliberately using a logger initialised while TCCL=somewebapp is ok too.
In fact, it's nice as the operations performed by StandardContext on behalf of a
specific webapp are logged via that webapp's config.

However in that case it is necessary to ensure that the logger is *not* set
before the TCCL is configured, and is *always* reset before the TCCL is restored
to the container one.

What is happening now is that the Log object can be initialised while the
TCCL=webapp, then used later when code unrelated to that webapp is running.
*That* is very bad.

As it happens, this isn't a theoretical problem. It is happening to me right now
as I'm working on a project for my current client; a problem during webapp
initialisation for one webapp causes the entire tomcat instance to fail to start.

Please consider reopening this.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message