tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mturra <m.tu...@kion.it>
Subject Jk disable worker on status
Date Mon, 02 Mar 2009 14:55:29 GMT

I have a tomcat farm behind an apache httpd cluster, each apache http server
have a jk connector connected to three tomcat. 

Each tomcat have a max active session limit (let's say 10).

I configured a load balanced worker with three worker.
I would like to disable the worker related to the tomcat server that reach
the max active session limit.

I see the fail_on_status directive in jk doc
(http://tomcat.apache.org/connectors-doc/reference/workers.html). I can use
it to deactivate (stop) the worker on a status code, but all the previous
session on this tomcat will get an error and they will be redirected on
another worker loosing session data (sticky session is required by
application).

There is no disable_on_status directive or something that exclude a worker
only for request requiring new session?

Thanks in advance. 
Matteo
-- 
View this message in context: http://www.nabble.com/Jk-disable-worker-on-status-tp22289604p22289604.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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


Mime
View raw message