JKStatus bug - disabled=true with only one Tomcat?

[dh...@lexmark.com]

Hi,

It seems that if there is only one tomcat server connected via mod_jk and
disabled is set to true (ie disabled=1) for that server that this is
ignored and requests still make it through.

Is this a bug, or a feature?!

cheers,

David


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

Re: JKStatus bug - disabled=true with only one Tomcat?

[Rainer Jung <rj...@apache.org>]

It's a feature:

- disabled and stop attributes only work, when a worker is a balanced 
worker of an lb

- if an lb has only one balanced worker, then disabled is not being 
respected, because then every request would result in an error. Only if 
you set the only worker to stop, it will get no requests and all 
requests result in errors. This behaviour is not a deduction from the 
general rules, it's instead hard coded at the beginning of the decision 
code.

Cheers,

Rainer

dhay@lexmark.com wrote:
> Hi,
> 
> It seems that if there is only one tomcat server connected via mod_jk and
> disabled is set to true (ie disabled=1) for that server that this is
> ignored and requests still make it through.
> 
> Is this a bug, or a feature?!
> 
> cheers,
> 
> David
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org

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