And Apache will act like you described. It'll report Ok code 200 when
your Servlet Container is up and 503 or some other error code if it's
down. You just need to configure BigIP to watch for that code.
On Thu, May 1, 2008 at 2:04 PM, Bruce Atherton <[EMAIL PROTECTED]> wrote:
> Thanks, Serge. Sorr
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
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
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 con
