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=41939>. 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=41939 ------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 06:53 ------- Created an attachment (id=20001) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=20001&action=view) Simple War File That Demonstrates NPE Behavior on Reload I deployed this WAR on the 5.5.20 and 5.5.23 binary distributions. This WAR contains a simple servlet that contains a static reference to a Log instance. The vanilla binary of log4j 1.2.14 is on the classpath, so commons-logging is using the log4j log provider. The servlet runs as expected (it just prints a message to the client and prints the same message in the log). However, when I click on the reload link for the application in the manager web application, the context fails to reload with a NullPointerException. The NullPointerException traces back to log4j classes. Specifically, I discovered that there are several instances where static members of the log4j classes in question are improperly set to null by something outside of log4j and not re-initialized. -- 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]
