You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Di...@eurotours.at on 2013/03/06 17:03:17 UTC
mod_jk 1.2.37 never send ping rq
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
Re: mod_jk 1.2.37 never send ping rq
Posted by Igor Cicimov <ic...@gmail.com>.
> redhat 6.4 / 64bit, apache 2.2.15 and mod_jk 1.2.37 --> tomcat latest
>
> In case of RedHat also check for SELinux policy on the tomcat server. And
for other security things you might be running like maybe AppArmor etc.
RE: mod_jk 1.2.37 never send ping rq
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Ben Stringer [mailto:ben@burbong.com]
> Subject: Re: mod_jk 1.2.37 never send ping rq
> In your properties file above, you have set it to "1", but it should be
> set to "True".
True (or anything starting with t) and 1 are equivalent:
http://marc.info/?l=tomcat-dev&m=136258408431762&w=2
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: mod_jk 1.2.37 never send ping rq
Posted by Ben Stringer <be...@burbong.com>.
> 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
>
Hi Dietmar,
It sounds to me that socket_keepalive is what you are after.
In your properties file above, you have set it to "1", but it should be
set to "True".
Cheers, Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: mod_jk 1.2.37 never send ping rq
Posted by Igor Cicimov <ic...@gmail.com>.
On 07/03/2013 4:25 PM, "Christopher Schultz" <ch...@christopherschultz.net>
wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Igor,
>
> On 3/6/13 9:02 PM, Igor Cicimov wrote:
> > On Thu, Mar 7, 2013 at 3:03 AM, <Di...@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.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEAREIAAYFAlE4IxgACgkQ9CaO5/Lv0PA0XwCgmx2kFWnfERmGvUWNhrNtPQt1
> yuUAn21J7iyaB8jyOEVv8+KC/tvJNfyB
> =s4Eq
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Antwort: Re: mod_jk 1.2.37 never send ping rq
Posted by Di...@eurotours.at.
Christopher Schultz <ch...@christopherschultz.net> schrieb am 07.03.2013
06:18:16:
> Von: Christopher Schultz <ch...@christopherschultz.net>
> An: Tomcat Users List <us...@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, <Di...@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
>
Re: mod_jk 1.2.37 never send ping rq
Posted by Igor Cicimov <ic...@gmail.com>.
On 07/03/2013 4:25 PM, "Christopher Schultz" <ch...@christopherschultz.net>
wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Igor,
>
> On 3/6/13 9:02 PM, Igor Cicimov wrote:
> > On Thu, Mar 7, 2013 at 3:03 AM, <Di...@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.
>
> - -chris
Thanks Chris for correcting me i thought they are separate.
Re: mod_jk 1.2.37 never send ping rq
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Igor,
On 3/6/13 9:02 PM, Igor Cicimov wrote:
> On Thu, Mar 7, 2013 at 3:03 AM, <Di...@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.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEAREIAAYFAlE4IxgACgkQ9CaO5/Lv0PA0XwCgmx2kFWnfERmGvUWNhrNtPQt1
yuUAn21J7iyaB8jyOEVv8+KC/tvJNfyB
=s4Eq
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: mod_jk 1.2.37 never send ping rq
Posted by Igor Cicimov <ic...@gmail.com>.
On Thu, Mar 7, 2013 at 3:03 AM, <Di...@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.