Antonio Fiol Bonnín wrote, On 3/11/2004 11:11 PM:
Tomcat will
detect the closed connection and return that JK thread back to the pool
for later use.
It won't. If the firewall has already dropped the connection, Tomcat
will not notice it being closed.
OK, so if the conn is dropped, TC won't know
.
-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
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
That won't help.
socket_timeout tells Apache to CLOSE connections that have been unused
for that time, but only WHEN it needs it.
So that will cause problems on the Tomcat side.
What we did (but our problem was slightly different) was:
Set the tcp keepalive sysctl of the web server (it is a
Antonio Fiol Bonnín wrote:
That won't help.
I think it will, see below.
socket_timeout tells Apache to CLOSE connections that have been unused
for that time, but only WHEN it needs it.
So that will cause problems on the Tomcat side.
Why will it cause problems on the Tomcat side?
IMO, it
socket_timeout tells Apache to CLOSE connections that have been unused
for that time, but only WHEN it needs it.
So that will cause problems on the Tomcat side.
Why will it cause problems on the Tomcat side?
See below.
IMO, it has a good chance of fixing the problem as Apache/mod_jk will
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=X.XXX.hp.com
worker.frontend.type=ajp13
worker.frontend.port=8007
Try setting the socket_keepalive and socket_timeout options and see if
that
