https://issues.apache.org/bugzilla/show_bug.cgi?id=43867
--- Comment #64 from Curt Arnold <[EMAIL PROTECTED]> 2008-08-07 20:20:09 PST --- I've committed a change in rev 683811 that adds a faq on NPE's and NOPLoggerRepository warnings during class unloading. Bug 40212 which originally resulted in the NOPLoggerRepository warning that this bug complained about does show several other non Tomcat related scenarios that can result in log4j having its class invariants violated. This isn't just a Tomcat issue. Other bugs show that class invariants can be violated outside of Tomcat unload calls. Per comment #58. I reviewed the current trunk implementation of WebappClassLoader.clearReferences and I think that Tomcat might be able to address the problem doing two passes on iterating through the loaded classes. One pass that would trigger class initialization if it hadn't already occurred. This would succeed since log4j is still in a valid state. Then a second pass that actually sets the fields to null. Would appreciate comments on the FAQ, the detection of Tomcat shutdown and the possibility to eliminating the problem in Tomcat. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
