On Mon, 13 May 2002, Bernd Koecke wrote: > Sorry, I must say it again, for my environment it is an error, if a _switched > off_ tomcat got a request without a sessionid or with a session from another > node. Its not necessary that this tomact-apache tandem is
In the current code ( in jk2 ), if a worker is in 'disabled' state it'll only get requests with sessionid, as you need. If it is not disabled, but has a higher level ( == distance ), it'll still not get any new requests unless all closer workers are in error state. > update and start them up again. If there are no local/main worker I need an > error response and no routing to a switched off tomcat. Its possible that this > happens once per day. Setting the non-local workers in disabled state should do that. > I know this might be a special environment. I spent some time in jk1 to > build a working patch. Than I started looking in jk2. I'm not a good C Your patch looks ok. Would it be possible to remove the use of '0' as a special value, and keep only the main_worker_mode flag for that ? Also, what's the meaning of 'reject' flag ? Also it would be nice to get some documentation for the new settings. Regarding jk2 - I just want to know if the current solution is ok or what are still problems. For now the priority is getting the patch in jk1 so it can be released in 4.0.4 final ( so today or early tommorow I would like to close this issue ). Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
