tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohit Anchlia <>
Subject Re: fail_on_status question
Date Sun, 06 Jun 2010 01:52:05 GMT
On Sat, Jun 5, 2010 at 2:02 AM, Rainer Jung <> wrote:
> On 04.06.2010 01:30, Mohit Anchlia wrote:
>> In our present environment we have a WS and APP server. When request
>> comes in, WS sends it to APP server using mod_jk and then APP server
>> inserts it into JMS queue. So essentially APP server is also dependent
>> on JMS server which runs on the same box.
>> My question is can I use fail_on_status in to take
>> one of the APP servers out of service from mod_jk(WS) by returning
>> some Http error code as a response to a request when JMS server is
>> down and a request comes in? Since cping and cpong will still return
>> success would this mechanism of fail_on_status work?
> fail_on_status will trigger nevertheless. Otherwise it would be useless.

I didn't get this piece that fail_on_status will trigger nevertheless?
My understanding is that cping and cpong decide if to keep a worker in
error state or not. But http response code will be returned only when
http request comes in. To cping and cpong server is still up. So even
if app server return status same as configured for fail_on_status
cping and cpong will still not bring the worker in error state.

>> Are there any other suggestions?
> Do a little scripting, monitor your Appserver and JMS and use the jk-status
> interface to properly disable or stop the appropriate load balancer member.
> Rainer
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message