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=39616>. 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=39616 Summary: Tomcat holds open JAR file even after undeploy Product: Tomcat 5 Version: 5.5.17 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] My (Spring framework) webapp has a number of JAR files in WEB-INF/lib, one of which contains all the class files for my web application (including Jasper compiled JSP). I've noticed that after stopping and undeploying the application, Tomcat continues to hold an open file handle to the webapp's JAR file. This is evidenced by it not undeploying properly when running under Windows (sharing violation/file in use), and by the creation of .nfsxxxx files when the webapps directory is NFS mounted. Only by stopping Tomcat entirely can the application directory be removed. Although when the application is running normally this isn't a problem, in development when the app is deployed/undeployed many times it is proving very irritating. If the application is deployed with the class files under classes/ instead of inside the JAR then everything works as expected and the application can be undeployed OK. Is there a reason for Tomcat to hold an open filehandle to the JAR file, and can it be fixed? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
