tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22263] New: - autodeploy conflicts with manager undeploy/deploy cycle
Date Fri, 08 Aug 2003 21:25:11 GMT
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=22263>.
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.

Mime
View raw message