he! :)
Thanks everyone for your input - I will let you know the results.
--
View this message in context:
http://www.nabble.com/mod_jk-affinity-for-a-lamed-tomcat-instance-tf2581047.html#a7228699
Sent from the Tomcat - User mailing list archive
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
>
tus page to
manually disable it.
For example : MyOutOfMemoryListener.class { setAJPErrorState(true); }
--
View this message in context:
http://www.nabble.com/mod_jk-affinity-for-a-lamed-tomcat-instance-tf2581047.html#a7221335
Sent from the Tomcat - User mailing list a
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:
I have a load-balanced cluster of application servers configured via
mod_jk. If one of the application servers has a "soft" JVM error (for
instance OOME: PermGen), mod_jk seems to develop an unfortunate
affinity for this lamed instance (probably because this server is no
longer processing requests
