tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mturra <>
Subject Re: Jk disable worker on status
Date Mon, 02 Mar 2009 17:18:08 GMT

Rainer Jung-3 wrote:
> We don't get any invalidation information from the backend, neither do 
> we know, whether a request carrying a session id actually belongs to a 
> valid session.
> So we do not have any immediate way of limiting by session count.
>> There is no disable_on_status directive or something that exclude a
>> worker
>> only for request requiring new session?
> No, there is not. We could provide one, but it would only make sense, if 
> the webapp would provide us with a special indication, that the node 
> should be disabled. 
> Furthermore, disabled is a configuration state. You do not only want it 
> to be set automatically, but you also need a way of revoking it later.

I mean the web application use a Standard Session Manager property
to limit the session number.

When the limit is reached I catch the exception and return a http status
code 503 (Service Unavailable).
Like the fail_on_status the connector could try after the "recovery period"
to pass a new session request (without session information in the request)
to the disabled worker and test the status code returned.
If the status is not like previous the worker can pass to active state,
otherwise the worker remain disabled.


View this message in context:
Sent from the Tomcat - User mailing list archive at

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

View raw message