https://issues.apache.org/bugzilla/show_bug.cgi?id=41939
--- Comment #23 from Dan Armbrust <[EMAIL PROTECTED]> 2008-07-09 13:40:47 PST --- Could someone with knowledge of this bug read through this comment on a bug in Log4j? https://issues.apache.org/bugzilla/show_bug.cgi?id=43867#c39 I believe that this is an example of tomcat breaking other code due to the way that it clears references, when org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES is left to its default of "on". In this case, log4j prevents a null pointer, and simply logs an error. But other code could very easily take a null pointer for the same reason. It doesn't seem like the current implementation of clear references is safe to use. Comment #17 indicates that clearReferences is a workaround to a different bug, and won't be removed. Perhaps that should be re-evaluated. I now have to disable clearReferences on my tomcat installs on most of my webapps which use log4j to prevent users from seeing a scary looking error being logged by log4j. -- 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]
