The mod_jk worker documentation says, that the connection_pool_timeout setting should be kept in sync with the connectionTimeout attribute of the AJP connector of Tomcat's server.xml. I think this is wrong and it rather should be kept in sync with Tomcat's keepAliveTimeout attribute (which is also defined in milliseconds). In most cases this is not a real problem, because the keepAliveTimeout attribute is set by default to the same value as connectionTimeout is set. But of course this is just its default setting.
Hi, Can anybody confirm this is a bug ? Which value should be connectionTimeout in server.xml then ? I was reading the doc, and I was going to change all my ajp connector configurations to make it sense (connection_pool_timeout == connectionTimeout), but now I have the doubt Thanks!
Yes you are right: if a separate keepAliveTimeout is set, you have to adjust it according to your connection_pool_timeout. It is it not set, you should instead set the connectionTimeout. I have tried to clarify the mod_jk docs and the example configuration comments in r1647570. This will be part of version 1.2.41. Thanks for reporting this. Rainer