hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38231] - request doesn't timeout when response is slow
Date Thu, 12 Jan 2006 08:45:40 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38231>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38231


odi@odi.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From odi@odi.ch  2006-01-12 09:45 -------
Mike,

This is not a bug but intended behaviour - whether you expect something else or
not. The SO_TIMEOUT value of a socket refers to the time between packets (see
API Doc of java.net.Socket#setSoTimeout). So as long as packets arrive within
the set timeout the connection is kept alive. As a request consists of several
packets (at least 7 or so: 3 to establish a conn, 1 for req and 1 for resp, at
least 2 to close the conn) this timeout has nothing to do with the overal
request time.

There is currently no interface to set a request timeout: You have to control
timeouts from the outside and call HttpMethod.abort(). The TimeoutController
class could be useful to you.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org


Mime
View raw message