Skip to content

Correct timeout message #281

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ash2k opened this issue Apr 19, 2013 · 1 comment
Closed

Correct timeout message #281

ash2k opened this issue Apr 19, 2013 · 1 comment
Assignees
Milestone

Comments

@ash2k
Copy link
Contributor

ash2k commented Apr 19, 2013

com.ning.http.client.providers.netty.NettyAsyncHttpProvider.ReaperFuture throws TimeoutException with message "No response received after %s" using request timeout for it. This is very misleading and makes it hard to debug - in my case request was timing out because of the default connection timeout of 1 minute and the exception was saying about 600000 (10 minutes, my request timeout).
I think it may be better to use actual time that the request was "in flight" or at least min(requestTimeout, connectionTimeout). And also maybe add time unit (ms) to the message.

@slandelle
Copy link
Contributor

Will have to port on master

@slandelle slandelle reopened this May 21, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants