-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
A SocketTimeoutException occured after restart the network. #3378
Comments
I think we gotta fix this with HTTP/2 pings. Otherwise we can’t differentiate between a stalled stream and a stalled connection. |
@swankjesse :Can you please let us know the tentative release date for 3.9 |
It might be a few months. If you need something urgently please use a snapshot; everything but the API is stable. |
Very much looking forward to 3.9 |
Will implement with this: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I created a HTTP/2 connection, this connection remains open in a half-closed state (read time is 1 hour). After connected, I disable the network and restart. And then, I send a normal request, which was occured a SocketTimeoutException : timeout
java.net.SocketTimeoutException: timeout at okhttp3.internal.http2.Http2Stream$StreamTimeout.newTimeoutException(Http2Stream.java:593) at okhttp3.internal.http2.Http2Stream$StreamTimeout.exitAndThrowIfTimedOut(Http2Stream.java:601) at okhttp3.internal.http2.Http2Stream$FramingSink.emitFrame(Http2Stream.java:510) at okhttp3.internal.http2.Http2Stream$FramingSink.write(Http2Stream.java:481) at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.java:171) at okio.RealBufferedSink.write(RealBufferedSink.java:85)
The text was updated successfully, but these errors were encountered: