You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/06/06 12:45:43 UTC

DO NOT REPLY [Bug 37956] - Make 'set static fields to null' ClassLoader leak workaround behaviour configurable

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=37956>.
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=37956





------- Additional Comments From steffen.dienst@gmx.de  2006-06-06 10:45 -------
Hi,

I'd like to vote for this request. We have some problems with redeployment of a 
webapp that seems to result from this workaround. The webapp runs several 
threads (for example within JCS) that use Log4j with commons-logging. After the 
redeployment of the application these threads are trying to access the 
LogManager which results in a NPE as all the fields were set to null. So a 
possibility of disabling of the workaround would be really nice. I seem to have 
a problem accessing the anonymous cvs, so I can't offer any patches, sorry.

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org