Josh Gooding <josh.good...@gmail.com> wrote:
>Igor, > >I figured it out. If you set the deployOnStartup attribute to true, >but >the autoDeploy attribute to false, the war files that are in the >webapps >folder at the time of startup will load. Then you can run the manager >via >script (command line). Simply pass the undeploy command to the manager >to >the context you want to remove and let it finish. It will remove the >war >and the application directory. Then I ran the command to deploy again >via >curl. This time it waited until the entire war was uploaded before it >deployed it. > >It took me a while to figure out it was a combination of >deployOnStartup >and autoDeploy. Of course there was ZERO incling that this was the >problem >and I had to re-re-re-read the docs very carefully to figure this out. >Finally decided to try a hunch and it actually paid off. It might be a >good idea to add this to the wiki or some place with common trouble >shooting problems. Disabling autoDeploy might be necessary if you are manually copying the JARs but if you are deploying via the Manager it is meant to mark the Context as "serviced" during the upload that should prevent that Context being auto-deployed. The Manager will then deploy it once the upload has completed. We need to figure out why the Manager isn't behaving as expected in this case. >> > When I run the command: curl -k --upload-file ROOT.war >> > https://[manageruser]:[pwd]@[fqd >> > name]:8443/manager/text/deploy?path=/ROOT&war=ROOT.war&update=true I don't see anything obviously wrong here but I haven't checked the code or the documentation yet. >> > Obviously there is something that I am doing wrong, but I can't figure it >> > out. While that is always a possibility - ;) - a Tomcat bug is also a possibility. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
