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] 2004-02-27 05:37 ------- Hi Dan, If you are seeing a jar that is locked, it means that some thread is still has a handle to some resource in that jar (or the thread is created from a class in the jar). The fact that this isn't happening when you put the jar in WEB-INF/classes should be obvious. The jar was never loaded from WEB-INF/classes. Plain classes are loaded there, not jars. You need to make sure what is still holding a handle to a resource in that jar and make sure it gets shut down at webapp shutdown. Remy is correct in saying that most of the issues here are due to user error, not a problem in Tomcat. That is not to say that this is necessarily true in all cases, but certainly most. Jake --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
