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 17:31 ------- Hi Jacob, I think you misunderstood what I was saying. We expanded the jar file into WEB-INF/classes. That is, "jar -xf my.jar". We then removed the jar file from WEB-INF/lib. Therefore, any resources that were previously being loaded from the jar file would now be getting loaded from the classes directory. However, whereas the jar file would be locked after undeploy in the previous case, we now see undeploy happen successfully when the jar file is expanded. If it were any of our threads holding a resource open, it still would have it open in the classes directory. The only difference we should have seen were that individual files would have been locked. We arrived at this point after having eliminated several cases where our threads were holding resources open. We've now verified this by getting a thread dump on threads still around after the undeploy. Also, we have no problem in running the exact same scenario in WebLogic. We're still investigating the problem and should have more info from a profiling tool pretty soon. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
