Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <481A2238.9070902@callenish.com>
Date: Thu, 01 May 2008 13:04:08 -0700
From: Bruce Atherton <bruce@callenish.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: users@httpd.apache.org
References: <481A1677.1080306@callenish.com>
 <868cbbaa0805011231u72eda187n4d798d357fc8666e@mail.gmail.com>
In-Reply-To: <868cbbaa0805011231u72eda187n4d798d357fc8666e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] Configure Apache to propagate servlet down
 condition
 back to load balancer

Thanks, Serge. Sorry for being off-topic, but I didn't know whether the 
solution lay in configuring Apache or not. It seemed like Apache was the 
intermediary between the two systems, and so seemed like the logical 
place to detect the failure of one system and pass it on to the other. I 
am glad that a better solution exists.

Thanks for your help.

Serge Dubrouski wrote:
> I think it's quite possible and fairly easy. BigIP allows you to
> create a custom HTTP/S monitors for a particular URL. So create a
> monitor that will get not just "/" but some URL that point to your
> Servlet Container and then set up a "Receive String" to expect
> something like "200 OK". So in case if your Servelet Container goes
> down Apache will answer with 503 error code, BigIP wont see 200 and
> will mark that particular member as down.
>
> Sorry, this item is little bit an off topic for this forum because it
> mostly relates to BigIP, not to Apache.
>
> On Thu, May 1, 2008 at 1:13 PM, Bruce Atherton <bruce@callenish.com> wrote:
>   
>> I have the following configuration:
>>
>>    BIG-IP   ->  Apache HTTPD  ->  Servlet Container
>>     Load    ->  Apache HTTPD  ->  Servlet Container
>>   Balancer  ->  Apache HTTPD  ->  Servlet Container
>>
>>  The Apache HTTPD instance serves up static content and translates HTTPS
>> requests into HTTP. Dynamic content is proxied to a Servlet Container
>> running an application.
>>
>>  My problem is that when one of the servlet containers seizes up, the BIG-IP
>> box doesn't take the Apache instance out of circulation. Instead, users are
>> continually connected to non-responsive servlets.
>>
>>  Is there any way to configure Apache so that it is identifies itself as
>> unavailable to the BIG-IP box if it finds that all proxy requests are
>> failing?
>>
>>  Thanks for any help.
>>
>>
>>  ---------------------------------------------------------------------
>>  The official User-To-User support forum of the Apache HTTP Server Project.
>>  See <URL:http://httpd.apache.org/userslist.html> for more info.
>>  To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
>>  For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>>     
>
>
>
>   


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org