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 what to do with it as it will sit there and wait forever for input. I can't find any options in the JK connectors to change the behavior of the server... The easy solution should be to add an option to enable keep alive on the server side as well.
And as I said (and sources seem to agree with me ;-), socket_timeout is only checked synchronously, i.e. at usage time. So, maybe socket_timeout=10, but you may have connections staying up for ... as long as a whole night of deep inactivity.
Good point, I did not think of that.
In the morning, if you "netstat" on both machines, you will see a different number of ESTABLISHED connections. You will have more of them in the Tomcat side. And that is not good. Add up some nights, and you will have to restart your tomcat server in a couple of days / a week / a couple of weeks, depending on your MaxSpareClients (or equivalent) in your web server and your maxProcessors / maxThreads in Tomcat.
Yeah, that's not good. Although it's better than having the server get stuck after only a few minutes of idle time. ;-)
-Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
