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 19230] - httpClient failed to reconnect after keep-alive connection timed out
Date Mon, 28 Apr 2003 19:01:18 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19230

httpClient failed to reconnect after keep-alive connection timed out





------- Additional Comments From becke@u.washington.edu  2003-04-28 19:01 -------
This purpose was to "fix" this problem by not allowing these connections to be
reused.  We decided "I believe in the IRC meeting" that this was the way to go.
 The reason being that since tunneled+HTTPS connections cannot be reused
reliably they should not be reused.  

The main problem case WAS when a method got a previously used connection (that
had timed out) and tried to use it.  This would cause the method to fail, with
the only feasable solution being to retry in HttpClient.  Since we were waiting
to push the retry logic into HttpClient this was also put off.  Thus the fairly
lousy solution.

The reason I say "WAS" above is that I think we can fix this now.  I think, now
that we have the ability to test for stale connections, this can be handled by
HttpClient.  HttpClient is currently calling HttpConnection.isOpen() in
execute(), which should preemptively take care of stale tunneled+HTTPS
connections.  I believe that if we remove the force close in
HttpConnection.releaseConnection() we may have a viable solution.  At least for
people who are using HttpClient (not the connections directly) and also have JRE
1.4 or better.

Mike

Mime
View raw message