You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2008/01/25 19:15:24 UTC

DO NOT REPLY [Bug 43867] - NOPLoggerRepository error during shutdown

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=43867>.
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=43867





------- Additional Comments From daniel.armbrust.list@gmail.com  2008-01-25 10:15 -------
For me, the argument goes like this:

Log4j has errors when a tomcat container is shutdown which contains log4j.  

These errors used to be silent - so no issue.

Now, in 1.2.15, they are being logged - which is a problem for me as well.

Suddenly, my customers are calling the help desk and asking what is this new error?

Log4J needs to be able to be shutdown without logging (and preferably, without
throwing) errors like this.

If someone can tell me what in my webapp would cause this, I'm happy to fix it.
 But this appears to be a tomcat / log4j bug, from what I have learned so far.

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