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=40212>. 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=40212 ------- Additional Comments From [EMAIL PROTECTED] 2007-08-23 11:38 ------- I also don't think this is a log4j issue but the NPE usually happens when something is wrong with the classloader (keeping a static reference to log4j while the webapp is reloaded or loading log4j in one classloader and then trying to log from another). Therefore, I suggest to add a check for a null value here and throw an IllegalStateException() with this message: "repositorySelector is null. This can only happen if log4j classes are used from two different classloaders. Look for stale static references to loggers and make sure that all loggers are loaded via the same classloader." That won't fix the issue but will make it much more straightforward to fix the real problem. -- 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]
