Rainer Jung wrote:
I still don't have a consistent idea what happened around the firewall:
It is a very simple: 1. There are firewalls that will cut the connection between mod_jk and Tomcat without sending FIN. You can not do anything with that, cause they simply exist, and I don't care why they exist. 2. Only the Tomcat is affected cause mod_jk connects to it. With mod_jk if write() fails we reconnect, but Tomcat still waits on stream read() and disconnects on some systems after 240 secs, thus rising the thread count. 3. Up to 1.2.18 even the httpd restart could cause thread count to double in size. So, having that, the only solution is to: 1. Set connectionTimeout in Tomcat that will always close the inactive connections 2. Use CPING/CPONG to detect disconnected sockets prior sending request. Now, the advanced thing should set the reuse flag to false according to the maxKeepAliveRequests in returned AJP packet. This will cause both Keep-Alive to work and graceful socket disconnection because both sides will be closed.
- no comments on my suggestion to make the connection pool more flexible: min pool size, max pool size and max connection number? this will allow us to - temporarily connect although the pool is expired with a defined limit - configure for not reusing connections by setting max_idle to 0
We have that already in 1.2.18. Regards, Mladen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
