Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 81811 invoked from network); 5 Nov 2008 17:15:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Nov 2008 17:15:53 -0000 Received: (qmail 27807 invoked by uid 500); 5 Nov 2008 17:15:48 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 27783 invoked by uid 500); 5 Nov 2008 17:15:48 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 27772 invoked by uid 99); 5 Nov 2008 17:15:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Nov 2008 09:15:47 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of HSivapatham@empirix.com designates 12.38.203.54 as permitted sender) Received: from [12.38.203.54] (HELO empbedex1.empirix.com) (12.38.203.54) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Nov 2008 17:14:31 +0000 Received: from EMPBEDEX.empirix.com ([10.16.0.92]) by empbedex1.empirix.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Nov 2008 12:08:35 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C93F69.202AB331" Subject: Designing tomcat failover Date: Wed, 5 Nov 2008 12:10:18 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Designing tomcat failover Thread-Index: Ack/aWD7fySIyu5mRReAoAslI7dMcQ== From: "Sivapatham, Hari" To: X-OriginalArrivalTime: 05 Nov 2008 17:08:35.0734 (UTC) FILETIME=[238D2B60:01C93F69] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C93F69.202AB331 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I have to design a failover setup and I am looking for rough ideas/pointers. Here is our scenario... =20 TomcatServer1 <-------/Cannot communicate to one another/-----> TomcatServer2(hot backup) ^ ^ ^ | \ |=20 | \ --- TO DO: Switch to TomcatServer2 if server 1 is down---| | \ / TomcatClient1 TomcatClient2 =20 (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).=20 - We have a redundant TomcatServer2 that is a hot backup for server1.=20 - 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). =20 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.=20 =20 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 failover. =20 I appreciate any ideas you might suggest. Thanks! Hari =20 =20 ------_=_NextPart_001_01C93F69.202AB331--