You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
com.ning.http.client.providers.netty.NettyAsyncHttpProvider.ReaperFuture
throwsTimeoutException
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.
The text was updated successfully, but these errors were encountered: