tree cd0153f7f6f313494fa82d94b45af019acac4826
parent 49bd35072553aaadfabbc3a09761632897169783
author Jesse Wilson <jessewilson@google.com> 1323983736 -0500
committer Jesse Wilson <jessewilson@google.com> 1323984661 -0500

Change the way we cope with stale pooled connections.

Previously we'd attempt to detect if a connection was stale by
probing it. This was expensive (it relied on catching a 1-millisecond
read timing out with a SocketTimeoutException), and racy. If the
recycled connection was stale, the application would have to catch
the failure and retry.

The new approach is to try the stale connection directly and to recover
if that connection fails. This is simpler and avoids the isStale
heuristics.

This fixes some flakiness in URLConnectionTest tests like
testServerShutdownOutput and testServerClosesOutput.

Bug: http://b/2974888
Change-Id: I1f1711c0a6855f99e6ff9c348790740117c7ffb9