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 [EMAIL PROTECTED]  2007-11-14 22:03 -------
The error message isn't the bug, it is a symptom of something else.  It is a 
notification that somehow that 
class invarients are being broken (likely by class reloading) and log4j is 
going to avoid throwing a NPE by 
substituting a minimal non-functional logger repository.  If this is happening 
at shutdown, then you have 
an annoying message but at least you didn't crash.  Not much log4j can do if a 
class loader is starting to 
mess with invariants other than to minimize the damage.  I'd expect that 1.2.14 
would raise 
NullPointerException under the same conditions that 1.2.15 would output a 
warning, but doesn't suprise 
me that things are a little inconsistent.  If the Tomcat community can either 
fix the classloader or give us 
specific instructions how to avoid their issue, we could have the problem go 
away, but there isn't much 
log4j can do to avoid the issue. 

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to