On 12.05.2012 17:34, kkoli...@apache.org wrote:
Author: kkolinko
Date: Sat May 12 15:34:31 2012
New Revision: 1337572
URL: http://svn.apache.org/viewvc?rev=1337572&view=rev
Log:
https://issues.apache.org/bugzilla/show_bug.cgi?id=53203
Correct documentation of default value of connectionTimeout for AJP protocol.
See org.apache.coyote.ajp.Constants.DEFAULT_CONNECTION_TIMEOUT
I am not sure though whether -1 is actually infinite and not some other (JVM?
OS?) default.
The timeout is implemented in Endpoint, and thus the implementation is shared with HTTP
protocol, and HTTP connectors documentation already says that -1 means infinite. So it is
likely that it is indeed "infinite".
It looks like: our value -1 trickles down into our class
SocketProperties. Before actually calling setSoTimeout on the socket,
the value is checked for being >=0. A negative values suppresses the call.
If we would call it with "-1", then we would get an
IllegalArgumentException from the JVM.
So "-1" just doesn't set the timeout and we end up with the OS default.
AFAIK that would mean infinite, because by default there is no socket
timeout in tcp, e.g. e read is allowed to block infinitely.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
