> From: peter_f...@blm.gov [mailto:peter_f...@blm.gov] > Subject: Misunderstanding deployOnStartup actions > > > I'm a bit confused about what the deployOnStartup setting is > supposed to do, especially when it's set to "false".
It defers webapp deployment until after the container is up and running. Some external event is required to trigger the deployment. > > if you set it to "false", then applications can only be > started by being hot-deployed No, you can use the manager or equivalent APIs to do the deployment, or you can configure the webapp in server.xml (not recommended). > I found that setting autoDeploy=true and deployOnStartup=false, > existing webapps are still started but not until after Tomcat > has already started As expected; the first request to the webapp triggers deployment. > I also found that setting autoDeploy=false and deployOnStartup=false, > no applications will start IIRC, any configured in server.xml will be started. > There's a couple of places in documentation (online, and also in the > O'Reilly book) where it says you shouldn't have hot-deployment AND > deployOnStart enabled because it can result in applications being > deployed twice Not true; double deployment occurs when you badly configure a webapp located in the appBase directory, such as having its <Context> element in server.xml with a path attribute that does not match the name of the .war file or directory. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
