Catch exception when reactor netty response is not available #14778
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SylvainJuge
approved these changes
Sep 24, 2025
...etry/javaagent/instrumentation/reactornetty/v1_0/ReactorNettyHttpClientAttributesGetter.java
Show resolved
Hide resolved
Co-authored-by: SylvainJuge <[email protected]>
mznet
pushed a commit
to mznet/opentelemetry-java-instrumentation
that referenced
this pull request
Sep 26, 2025
…lemetry#14778) Co-authored-by: SylvainJuge <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got notified that our rector netty http client instrumentation occasionally produces IllegalStateExceptions from
https://github.com/reactor/reactor-netty/blob/52d87512c6de3ef3f2990641bbfe997d95ab9262/reactor-netty-http/src/main/java/reactor/netty/http/client/HttpClientOperations.java#L549 I wasn't able to reproduce this (didn't try too hard). Looking at the code I got the impression that this could happen when the server responds with something that netty deems invalid (netty gets an exception while parsing the response).