We are getting the following entries in the logs frequently: [Sun Oct 15 09:31:35 2006] [6108:0516] [error] ajp_connection_tcp_get_message::j k_ajp_common.c (947): (worker2) can't receive the response message from tomcat, network problems or tomcat is down (172.17.96.97:9080), err=-60 [Sun Oct 15 09:31:35 2006] [6108:0516] [error] ajp_get_reply::jk_ajp_common.c (1 536): (worker2) Tomcat is down or refused connection. No response has been sent to the client (yet) [Sun Oct 15 09:31:35 2006] [6108:0516] [info] ajp_service::jk_ajp_common.c (182 8): (worker2) receiving from tomcat failed, recoverable operation attempt=0 [Sun Oct 15 09:31:35 2006] [6108:0516] [info] ajp_service::jk_ajp_common.c (186 7): (worker2) sending request to tomcat failed, recoverable operation attempt=1 [Sun Oct 15 09:32:07 2006] [6108:0516] [error] start_response::jk_isapi_plugin.c (554): HSE_REQ_SEND_RESPONSE_HEADER failed [Sun Oct 15 09:32:07 2006] [6108:0516] [error] write::jk_isapi_plugin.c (644): W riteClient failed with 00002746 [Sun Oct 15 09:32:07 2006] [6108:0516] [info] ajp_process_callback::jk_ajp_comm on.c (1410): Writing to client aborted or client network problems [Sun Oct 15 09:32:07 2006] [6108:0516] [info] ajp_service::jk_ajp_common.c (179 5): (worker2) request failed, because of client write error without recovery in send loop attempt=1 [Sun Oct 15 09:32:07 2006] [6108:0516] [info] service::jk_lb_worker.c (873): un recoverable error 200, request failed. Client failed in the middle of request, w e can't recover to another instance.
We are running isapi_redirect.dll version 1.2.19. This appears to the client user as a "hang" if you will. My research shows that this could be a network issue, but we've checked every last link the network, including all switch ports, load balancer, client connections, server connections, etc. My research also suggests that in 1.2.14 this was a load issue. We have very low load, perhaps up to 6 concurrent users at a time. Supposedly those using 1.2.18 have fewer issues? If anyone is using another version where they have seen this, and then resolved it with a later (or earlier) version, we'd love to hear about it. Anything to get rid of these periods of "hanging" would be really great! Configs: # An entry that lists all the workers defined worker.list=lb,jkstatus # Entries that define the host and port associated with these workers worker.worker1.host=server1 worker.worker1.port=9080 worker.worker1.type=ajp13 worker.worker1.connection_pool_size=100 worker.worker1.connection_pool_timeout=15 worker.worker1.socket_timeout=120 worker.worker2.host=server2 worker.worker2.port=9080 worker.worker2.type=ajp13 worker.worker2.connection_pool_size=100 worker.worker2.connection_pool_timeout=15 worker.worker2.socket_timeout=120 worker.lb.type=lb worker.lb.balance_workers=worker1,worker2 worker.lb.method=Busyness # Status worker for managing load balancer worker.jkstatus.type=status Thanks, -- -bk ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
