Bug 53203 - Incorrect document of ajp connectionTimeout.
Summary: Incorrect document of ajp connectionTimeout.
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: Documentation (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-08 01:46 UTC by Tatsuya Bessho
Modified: 2012-05-12 15:43 UTC (History)
0 users


Attachments
patch file (593 bytes, patch)
2012-05-08 01:46 UTC, Tatsuya Bessho 		Details | Diff
View All 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 Tatsuya Bessho 2012-05-08 01:46:43 UTC 
Created attachment 28739 [details]
patch file

The default value of AJP's connectionTimeout in the doc differs from the source code's.

Although the doc says "60000 ms", the source code says "-1".(i.e. no timeout).

I made the patch that corrects "60000 ms" to "no timeout" in the doc.
Comment 1 Konstantin Kolinko 2012-05-12 15:12:18 UTC 
I agree.

For reference, the value is

  org.apache.coyote.ajp.Constants.DEFAULT_CONNECTION_TIMEOUT = -1

and it is used in constructor of specific protocol implementation by calling setSoTimeout(Constants.DEFAULT_CONNECTION_TIMEOUT);
Comment 2 Konstantin Kolinko 2012-05-12 15:43:56 UTC 
Fixed and will be in 7.0.28.