Which version? If 1.2.28 or newer, look for error_escalation_time in
http://tomcat.apache.org/connectors-doc/reference/workers.html Read the description and try setting it to "0". Regards, Rainer On 31.03.2010 23:09, Mohit Anchlia wrote:
I am seeing weird behaviour here. What I am seeing is that when server is not pingable (when I reboot or shutdown) anymore mod_jk keeps logging errors 111 (connection refused) and errors 115 continuously and during this timeperiod if I look at "JkStatus" the State of the corresponding worker is still "OK" (which is incorrect in this case since server is not pingable). During this time period response times are still around 2-4 secs as compared to 300 ms. When everything is good our requests take 300 ms. Now once the server comes up (pingable) the state of the worker is "ERR" and at this point everything returns back to normal. So it looks like until server is pingable mod_jk doesn't put that worker in "ERR" state. So my question is what can I do in worker.properties such that worker goes in ERR state automatically when server or the machine completely goes down? It's kind of odd that mod_jk doesn't put the worker in ERR state when the box that worker is tied to is not pingable? --- worker.tc.type=lb worker.tc.balance_workers=host1,host2,host3,host4,host5,host6 worker.tc.sticky_session=true worker.host1.type=ajp13 worker.host1.port=8009 worker.host1.host=host worker.host1.socket_keepalive=true worker.host1.prepost_timeout=5000 worker.host1.connect_timeout=5000 worker.host1.retries=1 worker.host1.socket_connect_timeout=1000 worker.host1.connection_pool_minsize=0 worker.host1.connection_pool_timeout=20 worker.host1.recovery_options=7 worker.host1.ping_mode=A worker.host1.ping_timeout=5000 ... [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (10.10.81.153:8009) (errno=115) [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [error] ajp_send_request::jk_ajp_common.c (1467): (host5) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=115) [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [info] ajp_service::jk_ajp_common.c (2407): (host5) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1) [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [error] ajp_service::jk_ajp_common.c (2426): (host5) connecting to tomcat failed. [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [debug] ajp_reset_endpoint::jk_ajp_common.c (743): (host5) resetting endpoint with sd = 4294967295 (socket shutdown) [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [debug] ajp_done::jk_ajp_common.c (2850): recycling connection pool slot=0 for worker host5 [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [info] service::jk_lb_worker.c (1347): service failed, worker host5 is in local error state [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [debug] service::jk_lb_worker.c (1358): recoverable error... will try to recover on other worker [Wed Mar 31 13:39:15.517 2010] [19700:4143184544] [debug] get_most_suitable_worker::jk_lb_worker.c (969): found best worker host6 (host6) using method 'Request'
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
