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=34006>. 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=34006 Summary: Undeploy of webapps with antiResourceLocking in META- INF\context.xml fails after Tomcat restart Product: Tomcat 5 Version: 5.5.7 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] We have a webapp that needs to be dynamically redeployed on Windows, so we turned the antiResourceLocking option on in a context.xml file in its META-INF directory. Deployment/undeployment from a clean Tomcat works fine. However after stopping the Tomcat service and starting it again, we find that although the webapp is autoDeploy-ed correctly on startup (and unpacked into the \temp\ directory), it cannot be undeployed. The manager webapp reports a successful undeploy and there is no error message in any of the Tomcat logs; however the Manager's application list still includes the webapp, which appears to have been stopped but not undeployed. This behaviour seems to be the same whether or not antiResourceLocking is turned on globally. However if we either i) set antiResourceLocking=true in the global conf\context.xml file and remove the entire context.xml file from the webapp or ii) set antiResourceLocking=false in the webapp context.xml file, undeployment succeeds. (NB: unfortunately this does not provide a workaround for us, as we need antiResourceLocking=false globally to make other webapps work correctly) To demonstrate that this is a Tomcat problem and not specific to our apps, I have reproduced it using only the Manager webapp for the deploy/undeploy operations, with a stripped down webapp containing only a single JSP page, web.xml and the context.xml file. I'll upload this example .war shortly. I suspect the problem is related to the context files stored in the conf\enginename\host folder, as I note that deleting the webapp's context file from this folder seems to allow the undeployment to work correctly (whether it is deleted before or after starting Tomcat for the second time). -- 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]
