This defect was created in response to
https://github.com/influxdata/EAR/issues/2223
Getting tons of "REFUSED_STREAM caused by: okhttp3.internal.http2.StreamResetException: stream was reset: REFUSED_STREAM" errors in our application during standard reads some small percentage of the time (but thousands over about a month).
The defect indeed comes from the underlaying okhttp client library : square/okhttp#3955 . Going through all described occurrences of the same error, I think that we should better configure the client to use okhttp with HTTP 1.1 OOTB until a solution to square/okhttp#3955 is found. The customer reported that
options.getOkHttpClient().protocols(Collections.singletonList(Protocol.HTTP_1_1))
worked immediately, the errors dropped to 0.
Specifications:
- Client Version: any with okhttp 4.7.2
This defect was created in response to
https://github.com/influxdata/EAR/issues/2223
Getting tons of "REFUSED_STREAM caused by: okhttp3.internal.http2.StreamResetException: stream was reset: REFUSED_STREAM" errors in our application during standard reads some small percentage of the time (but thousands over about a month).
The defect indeed comes from the underlaying okhttp client library : square/okhttp#3955 . Going through all described occurrences of the same error, I think that we should better configure the client to use okhttp with HTTP 1.1 OOTB until a solution to square/okhttp#3955 is found. The customer reported that
worked immediately, the errors dropped to 0.
Specifications: