A month or so ago I posted that I was having problems with mod_jk (1.2.27) getting a pong response back from tomcat (6.0.18) in responses to a ping. Apache is 2.2.11 with worker mpm.
I have a little more information now and am hoping with help I can solve the problem so I can keep the ping timeout low and get rid of the error. Error does not show up when ping timeout is >= 25000. My tomcat connectionTimeout is set to 60000 My jkwatchdoginterval is set to 60 My relevant workers.properties is: worker.template.connection_pool_timeout=60 worker.template.reply_timeout=20000 worker.template.socket_timeout=10 worker.template.socket_connect_timeout=5000 worker.template.ping_mode=A worker.template.ping_timeout=10000 The mod_jk error is: [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] wc_maintain::jk_worker.c (339): Maintaining worker app-01 [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] ajp_maintain::jk_ajp_common.c (3081): reached pool min size 13 from 25 cache slots [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (1070): sending to ajp13 pos=4 len=5 max=16 [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (1070): 0000 12 34 00 01 0A 00 00 00 00 00 00 00 00 00 00 00 - .4.............. [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] jk_shutdown_socket::jk_connect.c (681): About to shutdown socket 52 [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] jk_shutdown_socket::jk_connect.c (732): Shutdown socket 52 and read 0 lingering bytes [Wed Apr 15 17:25:06 2009] [23222:1085466944] [info] ajp_connection_tcp_get_message::jk_ajp_common.c (1143): (app-01) can't receive the response header message from tomcat, tomcat (10.10.10.16:8009) has forced a connection close for socket 52 [Wed Apr 15 17:25:06 2009] [23222:1085466944] [info] ajp_handle_cping_cpong::jk_ajp_common.c (876): awaited reply cpong, not received [Wed Apr 15 17:25:06 2009] [23222:1085466944] [info] ajp_maintain::jk_ajp_common.c (3101): (app-01) failed sending request, socket -1 keepalive cping/cpong failure (errno=0) [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] ajp_reset_endpoint::jk_ajp_common.c (743): (app-01) resetting endpoint with sd = 4294967295 (socket shutdown) [Wed Apr 15 17:25:06 2009] [23222:1085466944] [debug] ajp_maintain::jk_ajp_common.c (3126): pinged 1 sockets in 0 seconds from 25 pool slots I send a request to tomcat via apache/mod_jk. Request's mount is mapped to worker, not loadbalancer. After successful request, Tomcat manager status shows the socket in stage 'R' and keeped alive socket count as 1. After 60 seconds, Tomcat manager status shows keeped alive socket count as 0, socket still in stage 'R' Above error happens 2 minutes after a request is finished, I'm assuming because the keep alive socket is not there anymore. So I set tomcat's connectionTimeout to 0 and repeat request. This time Tomcat (after 60 seconds) doesn't reset the keeped alive socket count to 0 (as expected), socket still in stage 'R'. 2 minutes later from mod_jk I get: [Wed Apr 15 17:30:08 2009] [23251:1102088512] [debug] wc_maintain::jk_worker.c (339): Maintaining worker app-01 [Wed Apr 15 17:30:08 2009] [23251:1102088512] [debug] ajp_maintain::jk_ajp_common.c (3081): reached pool min size 13 from 25 cache slots [Wed Apr 15 17:30:08 2009] [23251:1102088512] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (1070): sending to ajp13 pos=4 len=5 max=16 [Wed Apr 15 17:30:08 2009] [23251:1102088512] [debug] ajp_connection_tcp_send_message::jk_ajp_common.c (1070): 0000 12 34 00 01 0A 00 00 00 00 00 00 00 00 00 00 00 - .4.............. [Wed Apr 15 17:30:08 2009] [23251:1102088512] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1259): received from ajp13 pos=0 len=1 max=16 [Wed Apr 15 17:30:08 2009] [23251:1102088512] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1259): 0000 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - ................ [Wed Apr 15 17:30:08 2009] [23251:1102088512] [debug] ajp_maintain::jk_ajp_common.c (3126): pinged 1 sockets in 0 seconds from 25 pool slots At this point tomcat manager status shows the socket in stage 'P' and keeped alive socket count is 0. Above mod_jk log repeats every 2 minutes. Tomcat manager status doesn't change. Any help is appreciated. -Tony --------------------------- Manager, IT Operations Format Dynamics, Inc. 303-573-1800x27 abia...@formatdynamics.com http://www.formatdynamics.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
