On Wed, Mar 31, 2010 at 3:29 PM, Christopher Schultz <ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mohit, > > On 3/31/2010 5:33 PM, Mohit Anchlia wrote: >> On Wed, Mar 31, 2010 at 2:27 PM, Rainer Jung <rainer.j...@kippdata.de> wrote: >>> Which version? >>> >>> If 1.2.28 or newer, look for error_escalation_time in >> >> Actually I am on 1.2.27 so can't use error escalation time. Is there >> any other way I can do it? I am seeing real odd behaviour with mod_jk. >> It does change to ERR but only when box is pingable. Can't seem to >> find any other way of configuring it such that the failed worker is >> considered as global error. > > What happens if the backend server never comes back up? Try bringing it > down and waiting. How long does it take for mod_jk to put that worker > into ERR state? Or, are you actually required to bring-up the backend > server in order to achieve the ERR state?
I tested that leaving server down and in 15mt test the worker never went to ERR state while the node was down. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkuzzNEACgkQ9CaO5/Lv0PBOEgCgw6/ENt2t36dnG+9nRwNA7tCj > H1QAoMOOt0MDkjPSZr0gjQEZ/TRpQos/ > =+qy3 > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > 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
