To enable/disable via the status worker: Start /<status_worker_uri>?cmd=update&w=<workerName>&id=<workerPosIndex>&lb=0&wf=1 &wr=&wc=
Stop /<status_worker_uri>?cmd=update&w=<workerName>&id=<workerPosIndex>&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 > > <Caveat:This is only one option amongst many> > > 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: <users@tomcat.apache.org> > 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]
