Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of demablogia@gmail.com designates
 209.85.214.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8024_1345459477_50321515_8024_12499_1_50336698.9070901@yahoo.es>
References: <9283_1345458349_503210AD_9283_1227_1_50336231.4030205@yahoo.es>
 <CABOBwRihGqew2mN-8eKHXjP50ibzmEr1ViGae60dicpL=9eraw@mail.gmail.com>
 <8024_1345459477_50321515_8024_12499_1_50336698.9070901@yahoo.es>
From: =?ISO-8859-1?Q?Jose_Mar=EDa_Zaragoza?= <demablogia@gmail.com>
Date: Mon, 20 Aug 2012 12:58:09 +0200
Message-ID: 
 <CABOBwRh2E0R4xdbOPHz0fcXnWxF_c21YjY1GNvTYRgdYGF0daA@mail.gmail.com>
Subject: Re: redirecting people to maintenance mode
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

> maybe I haven't worded my idea correctly. I can't assume the Tomcat service
> in server1 is running all the time (since it's under maintenance, tomcat
> might be restarted a few times during the maintenance). That's why I thought
> about iptables. The issue is that iptables run at the IP level while
> redirects work at application level.
>

I thought that you only wanted to avoid that users access to server
,and if the server is down ...

In this case, I wouldn't have 2 server ( one for display a maintenance page ).
I'd prefer a frontend server , like Apache , and to use some module to
proxy /filter/check connection , etc.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org