On Wednesday 08 September 2010 22:49:20 Christopher Schultz wrote: > Rainer, > > On 9/3/2010 2:53 AM, Rainer Frey wrote: > > And if you use cold deployment only, how do you avoid downtime for other > > apps? Do you really use one Tomcat instance per app? > > I use one Tomcat instance per webapp, and I use cold deployment only.
I think this is the best way if you have the resources. But I need to host a growing number of rather small, new webapps, and have only one server ATM. Getting the memory config right that it is enough heap even in unexpected activity bursts, and still be able to run the required number of apps within the available RAM seems tricky. > > I'd really like to hear some input / experiences about production use > > with several applications with independent release/deploy cycles. > > I haven't done it, but Tomcat should be able to do hot re-deployment by > simply copying the new WAR file over the old one. Is that not an option > for you? No, a simple copy triggers no redeployment, as I use autoDeploy="false". I want to trigger the redeployment with the tomcat manager. As I stated in the first mail, that works, but is quite cumbersome: 1. undeploy current webapp with manager. This deletes war file, expanded directory, and conf/<Engine>/<Host>/app.xml 2. copy war file and (if needed) app.xml of new version to conf and appBase directory 3. deploy with manager, by specifying .war or .xml and the context path (that was already known to tomcat) What I was looking for is: 1. copy new .war and .xml 2. tell tomcat (manager) to update (redeploy) the already known application context with the new files (where redeploy includes updating/replacing the expanded directory) > -chris Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
