https://issues.apache.org/bugzilla/show_bug.cgi?id=43867
--- Comment #62 from Curt Arnold <[EMAIL PROTECTED]> 2008-08-06 21:57:43 PST --- >From comment #58 >But maybe we can hack our way out of this. Solution 1 would be to install a >listener which deinitializes log4j in such a way that any getLogger() call >would return null or a NOPLogger or something. >Solution 2 would be to create a private final static field which Tomcat will >eventually clear. If that field is cleared (and only Tomcat can do that since >it's private), you know that you're in the Tomcat shutdown cycle (instead of >some misconfiguration error) and you could ignore attempts to log anything >instead of throwing an error. log4j is already doing both of these things. It checks a private static field that should never be null through normal language mechanism for null and if it detects that it returns a NOPLogger instance. The complaint is that it emits a warning when it does so. If we knew that anytime that it encountered this scenario it was running in Tomcat and in clearReferences, we could just remove the warning or lower it to a debug severity. However, we can't say for certain that that is the only time it happens, we just know it is one place it happens. The last suggestion was to detect if it is in this one place that we know it happens and where we think the fallback behavior doesn't mask a bigger error and in that one scenario to reduce the severity of the message. -- 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]
