Re: mod_jk behaviour during failure

2010-04-03 Thread Rainer Jung
On 31.03.2010 23:33, Mohit Anchlia wrote: On Wed, Mar 31, 2010 at 2:27 PM, Rainer Jungrainer.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

Re: mod_jk behaviour during failure

2010-04-03 Thread Mohit Anchlia
On Sat, Apr 3, 2010 at 9:44 AM, Rainer Jung rainer.j...@kippdata.de wrote: On 31.03.2010 23:33, Mohit Anchlia wrote: On Wed, Mar 31, 2010 at 2:27 PM, Rainer Jungrainer.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

Re: mod_jk behaviour during failure

2010-04-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mohit, On 4/1/2010 5:04 PM, Mohit Anchlia wrote: On Thu, Apr 1, 2010 at 11:43 AM, Christopher Schultz ch...@christopherschultz.net wrote: The default is printed in the documentation:

Re: mod_jk behaviour during failure

2010-04-01 Thread Mohit Anchlia
On Wed, Mar 31, 2010 at 3:35 PM, Mohit Anchlia mohitanch...@gmail.com wrote: 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

Re: mod_jk behaviour during failure

2010-04-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mohit, On 4/1/2010 11:35 AM, Mohit Anchlia wrote: I tested that leaving server down and in 15mt test the worker never went to ERR state while the node was down. Could someone please advise? You'll have to wait for MLaden or Rainer to comment.

Re: mod_jk behaviour during failure

2010-04-01 Thread Mohit Anchlia
On Thu, Apr 1, 2010 at 11:43 AM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mohit, On 4/1/2010 11:35 AM, Mohit Anchlia wrote: I tested that leaving server down and in 15mt test the worker never went to ERR state while the node was

mod_jk behaviour during failure

2010-03-31 Thread Mohit Anchlia
I am seeing weird behaviour here. What I am seeing is that when server is not pingable (when I reboot or shutdown) anymore mod_jk keeps logging errors 111 (connection refused) and errors 115 continuously and during this timeperiod if I look at JkStatus the State of the corresponding worker is

Re: mod_jk behaviour during failure

2010-03-31 Thread Rainer Jung
Which version? If 1.2.28 or newer, look for error_escalation_time in http://tomcat.apache.org/connectors-doc/reference/workers.html Read the description and try setting it to 0. Regards, Rainer On 31.03.2010 23:09, Mohit Anchlia wrote: I am seeing weird behaviour here. What I am seeing

Re: mod_jk behaviour during failure

2010-03-31 Thread Mohit Anchlia
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

Re: mod_jk behaviour during failure

2010-03-31 Thread Christopher Schultz
-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

Re: mod_jk behaviour during failure

2010-03-31 Thread Mohit Anchlia
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