tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 41939] NPE in Logging due to classloading
Date Wed, 09 Jul 2008 20:40:48 GMT

--- Comment #23 from Dan Armbrust <>  2008-07-09 13:40:47
PST ---
Could someone with knowledge of this bug read through this comment on a bug in

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

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:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message