CONANT,PATRICK (HP-FtCollins,ex1) wrote: > 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?
Could you try setting the socket_timeout to an even lower value? Say 30s instead of 300? worker.frontend.socket_timeout=30 -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
