> We use apache http in-front of tomcat. This allows us to do exactly this. We > route calls from apache through to tomcat normally using mod_jk, and then > when we want to perform an upgrade, we update apache config, graceful > restart of apache, and apache routes all traffic to holding page. This won't > give you the ability to leave existing sessions running until completion.
I also have Apache httpd in front, but I don't want to kill sessions, as this is an ecommerce app. > I think what pid was suggesting was that you have you app deployed as > app##01.war. Then when it becomes upgrade time, create a second war file > with only a holding page in it, and deploy this as app##02.war. Old session > will continue until they die, and all new sessions will be directed the 02 > context. If this just sends to holding page, then you are done. When you are > ready, then roll out the proper app as app##03.war. Understood. > Personally I don't see what benefit this gives you. Does the upgrade perform > some kind of not backward compatible db change, surely you can just run app > v01 and app v02 side by side? What benefit does the holding page give you? Two benefits: 1) Allows incompatible upgrades. 2) Allos existing sessions to complete. > Chris -- Jonathan Rosenberg Founder & Executive Director Tabby's Place, a Cat Sanctuary http://www.tabbysplace.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
