Hello, I've discovered what appears to be a bug in mod_jk 1.2.27 and have also tried 1.2.30 without success. I'm using Apache 2.2.3 (on Redhat EL 5.4). The problem occurs after previous successful activity and causes a delay in what looks like socket handling. I noticed bug was resolved in 1.2.30 with respect to sockets but this does not appear to have solved the problem.
I've set the Jk logging to trace and you can see the debug statements and the 2s delays: [Mon Sep 06 15:05:12.121 2010] [24061:1404667232] [debug] wc_get_worker_for_name::jk_worker.c (116): found a worker lb-jboss51-integration [Mon Sep 06 15:05:14.128 2010] [24061:1404667232] [debug] wc_maintain::jk_worker.c (339): Maintaining worker lb-jboss51-integration [Mon Sep 06 15:05:14.241 2010] [23945:1404667232] [debug] wc_maintain::jk_worker.c (339): Maintaining worker lb-jboss51-integration [Mon Sep 06 15:05:16.644 2010] [23944:1404667232] [debug] wc_maintain::jk_worker.c (339): Maintaining worker lb-jboss51-integration [Mon Sep 06 15:05:18.131 2010] [24061:1404667232] [debug] init_ws_service::mod_jk.c (977): Service protocol=HTTP/1.1 method=GET ssl=false host=(null) addr=10.117.112.1 name=xxx port=80 auth=(null) user=(null) laddr=10.117.112.1 raddr=10.117.112.1 uri=/index.jsp [Mon Sep 06 15:05:18.131 2010] [24061:1404667232] [debug] get_most_suitable_worker::jk_lb_worker.c (997): found best worker jboss51-integration2 (jboss51-integration2) using method 'Request' Here's the workers.properties config: worker.basic.connection_pool_timeout=90 worker.basic.connection_pool_size=1 worker.basic.socket_keepalive=1 worker.basic.socket_timeout=90 worker.basic.connect_timeout=1000 worker.basic.prepost_timeout=1000 worker.basic.reply_timeout=90000 worker.basic.retries=1 worker.basic.recovery_options=27 worker.jboss51-integration1.reference=worker.basic worker.jboss51-integration1.host=xx worker.jboss51-integration1.port=13802 worker.jboss51-integration1.type=ajp13 worker.jboss51-integration1.lbfactor=1 worker.jboss51-integration2.reference=worker.basic worker.jboss51-integration2.host=yy worker.jboss51-integration2.port=13802 worker.jboss51-integration2.type=ajp13 worker.jboss51-integration2.lbfactor=1 worker.lb-jboss51-integration.type=lb worker.lb-jboss51-integration.balance_workers=jboss51-integration1,jboss51-integration2 worker.lb-jboss51-integration.sticky_session=0 worker.list=lb-jboss51-integration I've tried replacing connect_timeout, prepost_timeout and reply_timeout with ping_timeout, but this does not resolve the matter. I've tried commenting out various socket/connection settings, but have come to no firm conclusion to what may be at fault. The JBoss (5.1, but also a problem with 4.2.3) server.xml file has connectionTimeout="90000" set on the AJP connetor. Can anyone offer some advice? Or if I need to provide more information, please detail what is required. Many thanks, John --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
