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=8763>. 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=8763 Web app libraries (log4j.jar) remain locked after web apps' stop / remove Summary: Web app libraries (log4j.jar) remain locked after web apps' stop / remove Product: Tomcat 4 Version: 4.0.3 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, I have got automated deployment system that stops a web application and then replaces all the WEB-INF files the app is using (note I am not using a war archive) and starts the app. The problems is that when the app is stopped, Tomcat still keeps some of the lib files open (in my case it is only log4j.jar) and thus they cannot be overwritten by the deployment system. I also tried to stop the application and remove it, but the log4j.jar file still remains locked and cannot be removed. All the other files/libraries are successfully removed. It might as well be some log4j issue, but perhaps someone might be aware of its weird behaviour in Tomcat apps. Does Tomcat releases all context resources when the app is stopped? Or only when its removed? Thanks a lot, Jan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>