> What's possible though is making an http request to the status worker to
> disable or stop a worker. Unfortunately this change is not persistant
> concerning apache restarts.
This is an excellent solution - especially as the application servers are
restarted more often than Apache! :)
Thanks ev
opying of it or its
> contents
> - Original Message -
> From: "Dan Ackerson" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesday, November 07, 2006 11:19 AM
> Subject: Re: mod_jk affinity for a lamed tomcat instance
>
>
>> Sorry if I wasn't cl
al Message -
> From: "Dan Ackerson" <[EMAIL PROTECTED]>
> To:
> Sent: Tuesday, November 07, 2006 11:19 AM
> Subject: Re: mod_jk affinity for a lamed tomcat instance
>
>
>> Sorry if I wasn't clear - I wanted to know if their was a way I could
>>
error and that any review, disclosure, dissemination,
distribution or copying of it or its
contents
- Original Message -
From: "Dan Ackerson" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, November 07, 2006 11:19 AM
Subject: Re: mod_jk affinity for a lamed tomcat instance
>
Sorry if I wasn't clear - I wanted to know if their was a way I could
programmatically alert mod_jk from Tomcat that this worker should be
disabled. This way, the worker could automatically signal to mod_jk that it
was "lamed" and I wouldn't have to run over to the jk-status page to
manually disa
Hi Dan,
if mod_jk doesn't detect the error status of the tomcat instance,
because tomcat still sends valid http requests, you can set the worker
to disabled (no new sessions) or even stopped (no more requests).
By the way: I'm in Munich (W-JAX conference).
Regards,
Rainer
Dan Ackerson schrieb:
