Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of john.d.rellis@gmail.com
 designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50E7487A.2090907@christopherschultz.net>
References: 
 <CADRA4bUK=rFGoZe2_YVcyWAmymRvc+K47h_9_U5TeE8uA8fK3w@mail.gmail.com>
 <50E736B7.2000804@christopherschultz.net> <50E73A03.3090804@pidster.com>
 <50E7487A.2090907@christopherschultz.net>
From: John Rellis <john.d.rellis@gmail.com>
Date: Sun, 6 Jan 2013 16:18:18 +0000
Message-ID: 
 <CADRA4bX3XcoBoGpPR-KxhrgFv_fDayDFaXBwTDPrj7VOXPHnVw@mail.gmail.com>
Subject: Re: worker not marked as in error when shutdown with ping mode
 enabled
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=e89a8fb206a848ea1b04d2a11154

--e89a8fb206a848ea1b04d2a11154
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 4, 2013 at 9:24 PM, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Pid,
>
> On 1/4/13 3:22 PM, Pid wrote:
> > On 04/01/2013 20:08, Christopher Schultz wrote:
> >> On 1/3/13 10:54 AM, John Rellis wrote:
> >>>> I am using apache 2.2.3 and mod_jk as a load balancer for
> >>>> two tomcat 7 instances over AJP 1.3.
> >> Which exact version of mod_jk are you using? I'm guessing you
> >> are stuck on httpd 2.2.3 because of your package-manager? That's
> >> quite old.
> >
> > Some package managers report 2.2.3 despite it being a newer patch.
>
> ... though they usually only have the security-related patches, to
> keep things "stable".
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>
> iEYEAREIAAYFAlDnSHoACgkQ9CaO5/Lv0PDZNACguIruRN053z4eUu2I1I/wZTv2
> 8uYAnAw7UIQoBfr9elVtT2MrUYgaTMvB
> =Ttsr
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Hey,

Thanks for the response.

*Which exact version of mod_jk are you using? I'm guessing you are
stuck on httpd 2.2.3 because of your package-manager? That's quite old.*

I am using mod_jk/1.2.37.  Yes, I think I installed 2.2.3 because that is
what yum installed as I am using RHEL 5.

I didn't realise it was old so maybe I should look into upgrading it.

*How long is "a few minutes"?*
*
*
I shutdown one worker and waited 10 minutes and the worker was not marked
as unavailable, which I assumed ping_mode=A would do.


*You have not set any of the following:

connection_ping_interval
prepost_timeout
ping_timeout

The default for the first one is based upon the value for
ping_timeout. The defaults for the latter two are both 0 (zero).
Therefore, all these values are 0 for your setup.

Barring any bugs in your version of mod_jk (depends upon your
version), that should effectively disable periodic connection-pinging,
leaving you with only CONNECT and PREPOST testing.

Your ping_timeout is infinite (default=0=infinite) so depending upon
exactly what is happening with your Tomcat instance, you may wait
forever to set the worker to IN_ERROR.*


As far as I was aware, setting a ping_mode of A would then in turn set a
default value of 10,000 for ping_timeout.

In turn this would then set a connection_ping_interval of 100 seconds and a
prepost_timeout of 10,000.

I gathered this information from the docs page but maybe they don't match
up with my version????

http://tomcat.apache.org/connectors-doc/reference/workers.html

A prepost of 10,000 seems very high actually so I should probably change
that.

These values that I expected by setting a ping_mode of A do seem to be
populated in the jkmanager.  I will change them and see if I can have any
success

Many thanks!

John

-- 
John Rellis

--e89a8fb206a848ea1b04d2a11154--