DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3888>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3888 WebappClassLoader: Lifecycle error : CL stopped ------- Additional Comments From [EMAIL PROTECTED] 2002-10-12 05:18 ------- Would the fact that Tomcat is not nulling out the classloader fully upon application stop/remove/undeploy be the reason that the log4j jar in my webapp's WEB-INF/lib directory is being locked even after a stop/remove/undeploy? I only get this behavior with log4j. All other resources are let go. If this bug *is* the reason the log4j jar is being locked until after a full Tomcat shutdown, then it resolves a question that the Log4j developers and I have been asking about where the problem lies with the locked log4j jar file. If the culprit is Tomcat, then, I guess, we'd just wait for this bug to be fixed. If it is not, then I'd like to know that so we can direct our attention to finding the problem in Log4j. thanks, Jake -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
