Bug 50186 - Wrong documentation of connection_pool_timeout / connectionTimeout
Summary: Wrong documentation of connection_pool_timeout / connectionTimeout
Status: RESOLVED FIXED
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 1.2.30
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-31 08:55 UTC by Oliver Siegmar
Modified: 2014-12-23 13:23 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Siegmar 2010-10-31 08:55:32 UTC 
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.
Comment 1 i5513 2011-09-02 08:36:12 UTC 
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!
Comment 2 Rainer Jung 2014-12-23 13:23:33 UTC 
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