HttpClient TimeoutException message reports transient values #6382
Labels
Bug
For general bugs on Jetty side
Comments
sbordet
changed the title
sbordet
added a commit
that referenced
this issue
Jun 10, 2021
…alues. Now using consistently HttpConversation.getTimeout() to report the accurate value. Signed-off-by: Simone Bordet <[email protected]>
sbordet
added a commit
that referenced
this issue
Jun 21, 2021
…alues. Now using consistently HttpConversation.getTimeout() to report the accurate value. Signed-off-by: Simone Bordet <[email protected]>
sbordet
added a commit
that referenced
this issue
Jun 21, 2021
…alues. Now using consistently HttpConversation.getTimeout() to report the accurate value. Signed-off-by: Simone Bordet <[email protected]> (cherry picked from commit 734d3b6)
sbordet
added a commit
that referenced
this issue
Jun 21, 2021
…alues. Now using consistently HttpConversation.getTimeout() to report the accurate value. Signed-off-by: Simone Bordet <[email protected]> (cherry picked from commit 734d3b6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
9.4.42
Java version/vendor
(use: java -version)Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.7+8-LTS, mixed mode)
OS type/version
OSX 10.15.4
Description
When using the HttpClient to make asynchronous requests with a specific timeout, if the request has follow redirects enabled and the request ends up timing out; the error reported includes a timeout value that is different from the one specified on the request itself. This did not happen in older versions of Jetty. Example, you set a timeout of 5000ms on a request that ends up getting redirected and ultimately times out. The error message you'll receive will look like:
rather than:
How to reproduce?
You can run the test classes attached to #6323 and add a call to
result.getFailure().getMessage()in theonComplete()handler near the bottom of the test class.The text was updated successfully, but these errors were encountered: