At guidestar we cluster our tomcat sessions through the database. This allows us to shutdown one of the 5 tomcat servers without the users noticing because the other 4 servers seemlessly take on those user's requests. Any serious production site should be able to drop a server without their users noticing. Otherwise you have dead air. --Angus
> -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 08, 2004 8:16 AM > To: Tomcat Users List > Subject: RE: Best practices - doing code pushes > > > > Howdy, > I'm sure there are fancier ways, but I always opt for the > old-fashioned > way, which is to deploy and restart when no one is using the > application. This is almost always possible in an intranet > environment. > On the big web it's a different story, but I'd still probably > do it the > same way: analyze logs, pick a time of lowest usage, post a notice > before that time, and do it. > > Yoav Shapira > Millennium ChemInformatics > > > >-----Original Message----- > >From: Jacob Kjome [mailto:[EMAIL PROTECTED] > >Sent: Thursday, January 08, 2004 12:15 AM > >To: Tomcat Users List > >Subject: Re: Best practices - doing code pushes > > > >At 03:29 PM 1/7/2004 -0700, you wrote: > >>I have a question about how to load a new application w/o > interruption > of > >>service. > >> > >>What do others do to remove/reduce service interruption when doing a > new > >>code push? > >> > >>I would like to be able to push new code for new Axis services w/o > having > >to > >>kill any service requests currently being serviced, and pick up the > new > >code > >>for any new incoming requests. Is this possible? > >> > > > >There's a new "pause" parameter for the manager deploy servlet which > should > >do what you require... > >http://jakarta.apache.org/tomcat/tomcat-5.0-doc/manager- > >howto.html#Deploy%20A%20New%20Application%20Remotely > > > >Jake > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > This e-mail, including any attachments, is a confidential > business communication, and may contain information that is > confidential, proprietary and/or privileged. This e-mail is > intended only for the individual(s) to whom it is addressed, > and may not be saved, copied, printed, disclosed or used by > anyone else. If you are not the(an) intended recipient, > please immediately delete this e-mail from your computer > system and notify the sender. Thank you. > > > --------------------------------------------------------------------- > 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]
