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 Summary: request doesn't timeout when response is slow Product: HttpClient Version: 3.0 Final Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HttpClient AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] I've built an application around HttpClient that keeps statistics on all transactions performed. One of those statistics keeps track of the longest elapsed time of a single (non timed-out) request. I was often puzzled as to why this often exceeded the value I was using when calling setSoTimeout(). For example, I'd often call setSoTimeout() to timeout after 2000ms, but would often see single requests lasting over 3000ms. It appears that as long as data is trickling in on the response, it doesn't time out, and it takes (in the example above) 2000ms of inactivity before a request times out. This isn't the behavior I'd expect -- I would expect the request to timeout after 2000ms of elapsed time from the first byte recieved of the response. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
