tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sivapatham, Hari" <>
Subject Designing tomcat failover
Date Wed, 05 Nov 2008 17:10:18 GMT
I have to design a failover setup and I am looking for rough
ideas/pointers. Here is our scenario...
TomcatServer1  <-------/Cannot communicate to one another/----->
TomcatServer2(hot backup)
       ^         ^
       |           \
        |             \                      --- TO DO: Switch to
TomcatServer2 if server 1 is down---|
        |               \                   /
TomcatClient1     TomcatClient2
(Following text simply puts the above picture in words, in case it
doesnt show up aligned on some email clients)
- TomcatServer1 is a 5.5 tomcat that provides services. Its clients are
other tomcat instances (say TomcatClient1, TomcatClient2). 
- We have a redundant TomcatServer2 that is a hot backup for server1. 
- For simplicity sake, we can assume that there is no need to share
session information among TomcatServer1 and TomcatServer2. Also, for
practical reasons, we cannot have any communication between them (our
clients would resist opening up ports).
Our applications on TomcatClient1 and TomcatClient2 are configured to
talk to TomcatServer1. The task at hand is, the client tomcat instances
should automatically switch to TomcatServer2 if they detect that
TomcatServer1 is down. 
So, I am looking for a failover solution for outgoing requests from
TomcatClient1 and TomcatClient2. The only option I have right now is for
our apps to handle the failover. I wanted to check if there is some
module that I can use (filter/valve/apache module) that would handle the
I appreciate any ideas you might suggest.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message