-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matteo,
On 3/3/2009 12:32 PM, mturra wrote:
> But the LB worker doesn't know and continue to send request to this tomcat.
> I could use the session method for LB worker, but I have M apache httpd
> server connected to N tomcat (full-meshed) and I thin
Christopher Schultz-2 wrote:
>
> Rainer,
>
> On 3/2/2009 11:07 AM, Rainer Jung wrote:
>> I think a robust implementation would be something like:
>>
>> - a new state for temporarily disabling a node, except for sticky
>> requests
>>
>> - a configurable probe request, that the watchdog thread
Hi Chris,
On 03.03.2009 17:22, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 3/2/2009 11:07 AM, Rainer Jung wrote:
I think a robust implementation would be something like:
- a new state for temporarily disabling a node, except for sticky requests
- a co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rainer,
On 3/2/2009 11:07 AM, Rainer Jung wrote:
> I think a robust implementation would be something like:
>
> - a new state for temporarily disabling a node, except for sticky requests
>
> - a configurable probe request, that the watchdog thread s
Rainer Jung-3 wrote:
>
> 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 think a robust implemenation would be something like:
>
> - a new state for temporarily disabling a node, except for
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
On 02.03.2009 15:55, mturra wrote:
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 disab
