Apache 2.11, mod_jk/1.2.28: There seems to be a problem with activation of status worker JkStatus. Even after explicitly saying "stopped" for one of the workers the "Act" keeps going back and forth. When I refresh that page it keeps switching between "OK" and "STP". And I still see traffic being sent to that worker. Is this a known bug?
Earlier when we were on previous version of mod_jk this On Fri, Mar 6, 2009 at 2:02 PM, Rainer Jung <rainer.j...@kippdata.de> wrote: > On 06.03.2009 21:42, Mohit Anchlia wrote: >> >> In addition to questions that I have in below email, I have couple of >> question. >> >> 1. activation property disable - Does it first turn off new requests >> to that worker and then disable the worker after finishing old >> requests. So is this the best way to see 0 customer impact? >> 2. activation propery stopped - Does it throw away existing sessions >> and also stop taking new requests. > > Please read about activation on > > http://tomcat.apache.org/connectors-doc/reference/workers.html > > Stopped: do not allow any requests being send to the worker. > > Disabled: Only requests which carry a session, that is sticky on the worker > will go the the worker. No other requests will be send there. > > Use "disable" to dry out a worker, use "stoppped" directly before you > actually want to take it out of production. > >> Also I couldn't find way to see how mod_jk is behaving in the log >> file. I turned tracing on for JkLogLevel. > > I don't know what you mean by "behaving". > > Regards, > > Rainer > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
