Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 15385 invoked from network); 8 Aug 2003 21:22:27 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 8 Aug 2003 21:22:27 -0000 Received: (qmail 10943 invoked by uid 50); 8 Aug 2003 21:25:11 -0000 Date: 8 Aug 2003 21:25:11 -0000 Message-ID: <20030808212511.10942.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 22263] New: - autodeploy conflicts with manager undeploy/deploy cycle X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=22263 autodeploy conflicts with manager undeploy/deploy cycle Summary: autodeploy conflicts with manager undeploy/deploy cycle Product: Tomcat 5 Version: 5.0.6 Platform: Other OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: andy@xadra.com When autodeploy is enabled on the server, it creates contention with the manager deploy command when the "update=true" flag is set. When this flasg is set, the manager first performs and undeploy if necessary and then a deploy. After the undeploy, the autodeployer often redeploys the web application before the manager gets a chance to. This results in the manager, returning an error that the application is already deployed.