Turns out the Jetty (mortbay) configuration has a MaxTimeIdleMs setting. This sets the SO_TIMEOUT for the connection socket. The Jetty server was disconnecting from the client, leaving an unclean shutdown of the socket.
I found that the connection would sit in a FIN_WAIT2 state for a long time. BAD!! Reconfigured this for "0" so that the listener wouldn't timeout...kind of makes sense for busy sites! Now the client can disconnect after it's connection pool timeout. -- -bk -----Original Message----- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: Monday, October 16, 2006 8:29 AM To: Tomcat Users List Subject: Re: HSE_REQ_SEND_RESPONSE_HEADER failed Brandon, > 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 Is this intermittent, or does your AJP13 connection not work at all? Did it suddenly start happening, or has it been happening more and more over time? -chris ----------------------------------------------------------------------------------- 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]
