Just a guess: - Use Apache + mod_jk(2) + 2 tomcat instances
- Use sticky sessions (look at the jvmRoute of the engine tag) - Use the load factor to distribute 100% of the requests to the first instance. - Update the second instance. - Change the load factor to distribute 100% of the requests to the second instance. - Wait after all session moved to the second instance update the first instance and reverse the I haven't tried any of this but as far as I can remember I have seen posts in this list that indicate that this should be possible. > -----Original Message----- > From: Christian Mittendorf [mailto:[EMAIL PROTECTED] > Sent: Friday, October 01, 2004 12:15 PM > To: [EMAIL PROTECTED] > Subject: Howto deploy a new version of my webapp without > disturbing the > customer? > > > Hello! > > My scenario is an order application, where my customers can order > products. But the software or the design of the pages are changing > rapidly. The question is now: how can I deploy a new version without > the customer noticing anything? > > I'm searching for something similar to what WebObjects is > offering. WO > allows me to start a new instance (using the new version) of my > application in parallel to the already running application. All new > connections are then redirected to this new application. The existing > sessions in the old application can continue their order > process. When > the number of open sessions in this old instance reaches zero, the > instance is shut down. The customer out in the web does not > see that a > new version has been deployed. > > Is something simlilar possible using Tomcat? > > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
