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 (athena.apache.org: local policy)
In-Reply-To: <51382318.9000304@christopherschultz.net>
References: 
 <OF92CD6648.38F5EE01-ONC1257B26.0056E05B-C1257B26.0058310D@eurotours.at>
 <CAAKASGw_dGhqL=KXqnA39AmFEMvzXfvWY7TfRiuNpkiEyYcV5A@mail.gmail.com>
 <51382318.9000304@christopherschultz.net>
To: "Tomcat Users List" <users@tomcat.apache.org>
MIME-Version: 1.0
Subject: Antwort: Re: mod_jk 1.2.37 never send ping rq
Message-ID: 
 <OFB0C04DE1.D63276C7-ONC1257B27.0027C83D-C1257B27.00281521@eurotours.at>
From: Dietmar.Mueller@eurotours.at
Date: Thu, 7 Mar 2013 08:17:48 +0100
Content-Type: multipart/alternative;
 boundary="=_alternative 0028151EC1257B27_="

--=_alternative 0028151EC1257B27_=
Content-Type: text/plain; charset="US-ASCII"

Christopher Schultz <chris@christopherschultz.net> schrieb am 07.03.2013 
06:18:16:

> Von: Christopher Schultz <chris@christopherschultz.net>
> An: Tomcat Users List <users@tomcat.apache.org>, 
> Datum: 07.03.2013 06:25
> Betreff: Re: mod_jk 1.2.37 never send ping rq
> 
> * PGP Signed by an unknown key
> 
> Igor,
> 
> On 3/6/13 9:02 PM, Igor Cicimov wrote:
> > On Thu, Mar 7, 2013 at 3:03 AM, <Dietmar.Mueller@eurotours.at>
> > wrote:
> > 
> >> hi all
> >> 
> >> i setup apache <--> mod_jk <--> tomcat the firsttime with
> >> firewall. what i saw was a not working page. after search and
> >> read the mod_jk docs i see and found the reason. the firewall
> >> drop the jk connection. i try to set properties like keep_alive
> >> and ping but i never see with wireshark any package do exact the
> >> job, what i read from the doc (might i missunderstand something)
> >> --> send after some time a ping. i expect this on the ajp
> >> connection. i watch the complete traffic between apache and
> >> tomcat
> >> 
> >> my config is stright forward:
> >> 
> >> worker.list=jkstatus, tc
> >> 
> >> worker.jkstatus.type=status
> >> 
> >> worker.tc.type=lb worker.tc.balance_workers=1
> >> 
> >> worker.1.type=ajp13 worker.1.host=192.168.13.50 
> >> worker.1.port=8009 worker.1.socket_keepalive=1 
> >> worker.1.ping_mode=A worker.1.ping_timeout=10000 
> >> worker.1.connection_ping_interval=9000 
> >> worker.1.connection_pool_size=1
> >> 
> >> worker.2.type=ajp13 worker.2.host=192.168.13.51 
> >> worker.2.port=8009 worker.2.socket_keepalive=1 
> >> worker.2.ping_mode=A worker.2.ping_timeout=10000 
> >> worker.2.connection_ping_interval=9000 
> >> worker.2.connection_pool_size=1
> >> 
> >> i play with the values but i never see something periodical at
> >> the network side.
> >> 
> >> my system:
> >> 
> >> redhat 6.4 / 64bit, apache 2.2.15 and mod_jk 1.2.37 --> tomcat
> >> latest
> >> 
> >> any help / comment is wellcome
> >> 
> >> thanks dietmar
> > 
> > Well in this case I can think of only one reason of this not to
> > work: the firewall is dropping the ICMP packets. What kind of
> > firewall are we talking about here? Is it hardware one or the
> > iptables on tomcat server. Anyway, easy to test, switch off the
> > firewall and then check if you can see the pings.
> 
> Wrong, mod_jk does not use ICMP to "ping" the backend server. It uses
> (not surprisingly) TCP/IP packets using the AJP protocol.
> 

yes, this is also what i expect. i don't use ip tables and or local 
firewalls
on host. i use a hardware box between httpd and tomcat. i expect an ajp 
ping
with (and on) exact all open ajp connections, because the firewall drop 
the
unused ajp connections after some time. on other side mod_jk expect that 
the
connections already works and to know, that the connections are not alive 
mod_jk
have to run into a timeout first. and exact this need too long and is not
what i expect.

> -chris
> 
> * Unknown Key
> * 0xF2EFD0F0(L)
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 

--=_alternative 0028151EC1257B27_=--