logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 43867] NOPLoggerRepository error during shutdown
Date Mon, 07 Jul 2008 20:49:54 GMT

--- Comment #25 from Dan Armbrust <daniel.armbrust.list@gmail.com>  2008-07-07 13:49:53
PST ---
I'm sorry Aaron, but to borrow your pattern, I'm quite certain that this bug is
*not* *not* *not* *not* a bug in the deployed webapp - or anything to do with
users threads.

This is purely a problem between tomcat and log4j.  

By putting one of my apps into a debugger, I have concluded the following:

The error message in question

"log4j:ERROR LogMananger.repositorySelector was null likely due to error in
class reloading, using NOPLoggerRepository." 

is printed by the Main thread in the JVM.  

I know this because it happens when I have paused every other thread in the JVM
via the debugger.  So, lets just throw out this mystery threading problem

Furthermore, this error message is printed within the class:

org.apache.catalina.loader.WebappClassLoader.clearReferences() - between the
lines of 1596 and 1640 (in tomcat version 5.5.25) as it is being executed by
tomcats main thread during a tomcat shutdown.

Even if this was a mystery threading problem (which is isn't) your answer isn't
very helpful - in that case, the issue would be that the message being logged
sucks - and it should be improved to at least give a stack trace, or a thread
name, or something that could be used to actually track down the problem.

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

View raw message