You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Brandon Cruz <bc...@norvax.com> on 2002/07/25 16:02:08 UTC

Can two tomcats back each other up on one machine?

I am running tomcat 3.2.4 (I know it's old, but it works great!).  We
typically have around 50 database connections and twice as many sessions
going at any given time.  I would like to set up another tomcat, or find a
solution to restart without having to kill everyone's session.  Is there
anyway I can set up this up so that if one tomcat goes down for restart the
sessions can automatically be transferred over to the other tomcat?  After I
restart the first, then I can restart the second the same way.  The problem
is that we usually add two or three virtual hosts per day and need those
changes to be recognized.

Has anyone done anything like this before or run into the same problem?

Brandon



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Can two tomcats back each other up on one machine?

Posted by Luminous Heart <lu...@yahoo.com>.
I am not sure it is being done, but if we ask our
developers kindly *smile* they might put that task on,
or maybe tell us what needs to be done. I would
volunteer for this project as well.


--- Brandon Cruz <bc...@norvax.com> wrote:
> Thanks Tom,
> 
> I also saw that there was development under way to
> set up something that
> will replicate sessions across all tomcat instances.
>  I don't know how long
> ago that was written, does anyone know if that has
> happened yet?
> 
> Brandon
> 
> -----Original Message-----
> From: Tom Oinn [mailto:tmo@ebi.ac.uk]
> Sent: Thursday, July 25, 2002 9:05 AM
> To: Tomcat Users List
> Subject: Re: Can two tomcats back each other up on
> one machine?
> 
> 
> 
> 
> Brandon Cruz wrote:
> > I am running tomcat 3.2.4 (I know it's old, but it
> works great!).  We
> > typically have around 50 database connections and
> twice as many sessions
> > going at any given time.  I would like to set up
> another tomcat, or find a
> > solution to restart without having to kill
> everyone's session.  Is there
> > anyway I can set up this up so that if one tomcat
> goes down for restart
> the
> > sessions can automatically be transferred over to
> the other tomcat?  After
> I
> > restart the first, then I can restart the second
> the same way.  The
> problem
> > is that we usually add two or three virtual hosts
> per day and need those
> > changes to be recognized.
> >
> > Has anyone done anything like this before or run
> into the same problem?
> 
> Not sure about exactly how you do what you're
> describing, but another
> solution is as follows.
> 
> 1) set up a redirector with sticky session
> management, so requests are
> routed through to whichever container their session
> is bound to
> 
> 2) when you want to update your services, you don't
> shut down either
> container, you simply prevent new sessions being
> created on one or the
> other.
> 
> 3) when all active sessions have cleared from the
> unreachable container,
> you can shut it down and reconfigure it
> 
> 4) repeat in the obvious fashion for the other
> 
> It may be possible (well okay, it's possible, it may
> be easy) to
> automate this, and similarly it scales to multiple
> instances quite
> nicely. It's trivial if you have good hardware
> redirectors, but they're
> not exactly cheap bits of kit so it's entirely
> likely you don't.
> 
> Hope that's of some help,
> 
> Tom
> 
> 
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Can two tomcats back each other up on one machine?

Posted by Brandon Cruz <bc...@norvax.com>.
Thanks Tom,

I also saw that there was development under way to set up something that
will replicate sessions across all tomcat instances.  I don't know how long
ago that was written, does anyone know if that has happened yet?

Brandon

-----Original Message-----
From: Tom Oinn [mailto:tmo@ebi.ac.uk]
Sent: Thursday, July 25, 2002 9:05 AM
To: Tomcat Users List
Subject: Re: Can two tomcats back each other up on one machine?




Brandon Cruz wrote:
> I am running tomcat 3.2.4 (I know it's old, but it works great!).  We
> typically have around 50 database connections and twice as many sessions
> going at any given time.  I would like to set up another tomcat, or find a
> solution to restart without having to kill everyone's session.  Is there
> anyway I can set up this up so that if one tomcat goes down for restart
the
> sessions can automatically be transferred over to the other tomcat?  After
I
> restart the first, then I can restart the second the same way.  The
problem
> is that we usually add two or three virtual hosts per day and need those
> changes to be recognized.
>
> Has anyone done anything like this before or run into the same problem?

Not sure about exactly how you do what you're describing, but another
solution is as follows.

1) set up a redirector with sticky session management, so requests are
routed through to whichever container their session is bound to

2) when you want to update your services, you don't shut down either
container, you simply prevent new sessions being created on one or the
other.

3) when all active sessions have cleared from the unreachable container,
you can shut it down and reconfigure it

4) repeat in the obvious fashion for the other

It may be possible (well okay, it's possible, it may be easy) to
automate this, and similarly it scales to multiple instances quite
nicely. It's trivial if you have good hardware redirectors, but they're
not exactly cheap bits of kit so it's entirely likely you don't.

Hope that's of some help,

Tom


--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Can two tomcats back each other up on one machine?

Posted by Tom Oinn <tm...@ebi.ac.uk>.

Brandon Cruz wrote:
> I am running tomcat 3.2.4 (I know it's old, but it works great!).  We
> typically have around 50 database connections and twice as many sessions
> going at any given time.  I would like to set up another tomcat, or find a
> solution to restart without having to kill everyone's session.  Is there
> anyway I can set up this up so that if one tomcat goes down for restart the
> sessions can automatically be transferred over to the other tomcat?  After I
> restart the first, then I can restart the second the same way.  The problem
> is that we usually add two or three virtual hosts per day and need those
> changes to be recognized.
> 
> Has anyone done anything like this before or run into the same problem?

Not sure about exactly how you do what you're describing, but another 
solution is as follows.

1) set up a redirector with sticky session management, so requests are 
routed through to whichever container their session is bound to

2) when you want to update your services, you don't shut down either 
container, you simply prevent new sessions being created on one or the 
other.

3) when all active sessions have cleared from the unreachable container, 
you can shut it down and reconfigure it

4) repeat in the obvious fashion for the other

It may be possible (well okay, it's possible, it may be easy) to 
automate this, and similarly it scales to multiple instances quite 
nicely. It's trivial if you have good hardware redirectors, but they're 
not exactly cheap bits of kit so it's entirely likely you don't.

Hope that's of some help,

Tom


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>