-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark,
On 8/29/2011 9:37 AM, Mark Thomas wrote: > On 29/08/2011 04:15, Sammy MT Lau wrote: >> >> >> Hello all, >> >> I've read some articles regarding to the parallel deployment of >> tomcat 7. From what I've read, enabling parallel deployment >> requires the enablement of tomcat session as well. However, the >> API server and client I'm working with don't do any session >> management using the tomcat session. Therefore, I've the tomcat >> session disabled. So, what's the behaviour of parallel deployment >> when I just turned on the tomcat session without having the >> client ever do anything with the session id in url or cookie. In >> that case, all of the requests coming to the tomcat doesn't have >> any session info. I'm going to do some tests but if someone on >> the list could shed me some light on this would be highly >> appreciated. > > Requests will always go to the latest version of the web > application. In this scenario, there is little benefit to using > parallel deployment. I still see a use for parallel deployment: zero down-time. Webapp redeployment isn't instantaneous, especially if the webapp itself has a non-trivial startup time. Parallel deployment allows more seamless upgrades. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5bubQACgkQ9CaO5/Lv0PDsZACcCDMelwap3NlMvFnIkZTMsxwu AiMAoKghLsJrhWUUmrpSP4vg9HXhUXc2 =M6lv -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
