Thanks for the proposal. We made the change, but to no avail. When the IIS server came back up, we saw the same problem start almost immediately.
The only other report of this problem I could find was for a different product (http://www.firewall-1.org/2002-04/msg00180.html). I don't think that the cause could be the same: with the amount of traffic we're seeing, the JK connections should just remain open. Regardless, our firewall admin refuses to change the tcptimeout (as suggested in the above link) due to potential impacts on other applications. Any other ideas? Thanks, Pat. -----Original Message----- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 9:47 AM To: Tomcat Users List Subject: Re: JK Connector & SYN packet for established connection CONANT,PATRICK (HP-FtCollins,ex1) wrote, On 3/10/2004 7:58 AM: > > Our workers.properties file is pretty simple: > worker.list=frontend > worker.frontend.host=XXXXX.XXX.hp.com > worker.frontend.type=ajp13 > worker.frontend.port=8007 Try setting the socket_keepalive and socket_timeout options and see if that helps: worker.frontend.socket_keepalive=1 worker.frontend.socket_timeout=300 -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
