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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
  "   from the digest: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
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: [EMAIL PROTECTED]
  "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to