Re: mod_jk affinity for a lamed tomcat instance
> 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 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 at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod_jk affinity for a lamed tomcat instance
To enable/disable via the status worker:
Start
/?cmd=update&w=&id=&lb=0&wf=1
&wr=&wc=
Stop
/?cmd=update&w=&id=&lb=0&wf=1
&wr=&wc=&ws=on
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 5:04 PM
To: Tomcat Users List
Subject: Re: mod_jk affinity for a lamed tomcat instance
>From the docs about DisableReuse: "Using this option will have a strong
performance penalty for Apache and Tomcat. Use this only as a last
resort in case of unfixable network problems.".
Concerning the original queation: I don't see any clean and direct way
of doing that.
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.
The status worker is completely GET based, so you can look at your
browsers URL line, how the request for disabling a worker would look
like by doing it once in a browser.
Regards,
Rainer
Martin Gainty schrieb:
> Dan-
> the only way I could see accomplishing this task to programmatically
support socket_keepalive on the connection and use default config of quiesce
connection when not use ...as in this parameter which requests mod_jk to
close connections immediately after use as in this option
>
> JkOptions +DisableReuse
>
>
>
> Anyone else?
> M-
> This e-mail communication and any attachments may contain confidential and
privileged information for the use of the
> designated recipients named above. If you are not the intended recipient,
you are hereby notified that you have received
> this communication in 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 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 archive at Nabble.com.
>>
>>
>> -
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk affinity for a lamed tomcat instance
>From the docs about DisableReuse: "Using this option will have a strong
performance penalty for Apache and Tomcat. Use this only as a last
resort in case of unfixable network problems.".
Concerning the original queation: I don't see any clean and direct way
of doing that.
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.
The status worker is completely GET based, so you can look at your
browsers URL line, how the request for disabling a worker would look
like by doing it once in a browser.
Regards,
Rainer
Martin Gainty schrieb:
> Dan-
> the only way I could see accomplishing this task to programmatically support
> socket_keepalive on the connection and use default config of quiesce
> connection when not use ...as in this parameter which requests mod_jk to
> close connections immediately after use as in this option
>
> JkOptions +DisableReuse
>
>
>
> Anyone else?
> M-
> This e-mail communication and any attachments may contain confidential and
> privileged information for the use of the
> designated recipients named above. If you are not the intended recipient, you
> are hereby notified that you have received
> this communication in 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 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 archive at Nabble.com.
>>
>>
>> -
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk affinity for a lamed tomcat instance
Dan-
the only way I could see accomplishing this task to programmatically support
socket_keepalive on the connection and use default config of quiesce connection
when not use ...as in this parameter which requests mod_jk to close connections
immediately after use as in this option
JkOptions +DisableReuse
Anyone else?
M-
This e-mail communication and any attachments may contain confidential and
privileged information for the use of the
designated recipients named above. If you are not the intended recipient, you
are hereby notified that you have received
this communication in 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 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 archive at Nabble.com.
>
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
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 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 archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk affinity for a lamed tomcat instance
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 and looks fairly idle). > > How can I alert the AJP connector on the tomcat side that this app > server is dead so that mod_jk no longer routes requests to it? > > Thanks in advance, > > Dan > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
