palantir / palantir/conjure-java-runtime
Http2 calls against go server failing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 96
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 33
Description
What happened?
We use a conjure client to talk to a Go server. This call was working fine with Java 8. On upgrading to Java 11 on client side the call started failing with the following error:
INFO com.palantir.conjure.java.okhttp.RemotingOkHttpCall - Retrying call after failure
okhttp3.internal.http2.StreamResetException: stream was reset: PROTOCOL_ERROR
at okhttp3.internal.http2.Http2Stream.takeHeaders(Http2Stream.java:156)
at okhttp3.internal.http2.Http2Codec.readResponseHeaders(Http2Codec.java:137)
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:101)
It was suggested that this could be because of the server advertising Http2 compatibility and then conjure-java-runtime tries to use it when on Java11+. Disabling http2 on the server side fixed the issue.
What did you want to happen?
Http2 connections against Go servers should just work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Java 11 conjure client call against a Go server with HTTP/2 enabled, then compare it with the configuration where HTTP/2 is disabled. Done means HTTP/2 connections to Go servers complete successfully without the reported PROTOCOL_ERROR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- api, backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100