tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <>
Subject RE: Best practices - doing code pushes
Date Sat, 10 Jan 2004 01:10:51 GMT
At 10:28 AM 1/9/2004 -0700, you wrote:
>Thanks for the information. It looks like this is for Tomcat 5. We're using
>4. Is there any similar functionality in 4?

Not that I'm aware of.  I suggest moving to Tomcat5 if at all possible.  It 
is *so* much better.  I think you'll like it.


>Sean LeBlanc
>Software Developer
>"Those who do not understand Unix are condemned to reinvent it, poorly."
>--Henry Spencer
>-----Original Message-----
>From: Jacob Kjome []
>Sent: Wednesday, January 07, 2004 10:15 PM
>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...
>To unsubscribe, e-mail:
>For additional commands, e-mail:
>e-Mail Notice: This communication may contain sensitive information.  If you
>are not the intended recipient, or believe that you have received this
>communication in error, do not print, copy, retransmit, disseminate, or
>otherwise use the information contained herein for any purpose.  Please
>alert the sender that you have received this message in error and delete the
>copy that you received.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message