Rainer Jung-3 wrote: > > Furthermore, disabled is a configuration state. You do not only want it > to be set automatically, but you also need a way of revoking it later. > > I think a robust implemenation would be something like: > > - a new state for temporarily disabling a node, except for sticky requests > > - a configurable probe request, that the watchdog thread sends, and > which is answered by the application, the answer containing the > information whether the node should be temporarily disabled or not >
I agree a new state could be better. I used "disabled" because of its behavior: let the previous run and block the new coming. The probe is done retrying after a "quiet" period. Thanks, Matteo. -- View this message in context: http://www.nabble.com/Jk-disable-worker-on-status-tp22289604p22292526.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
