Fix Netty connection failure handling when listener is lambda #3569
Conversation
This file contains 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
laurit
requested review from
anuraaga,
iNikem,
jkwatson,
mateuszrzeszutek,
pavolloffay,
trask and
tylerbenson
as code owners
mateuszrzeszutek
approved these changes
Jul 14, 2021
...entelemetry/javaagent/instrumentation/netty/common/client/AbstractNettyHttpClientTracer.java
Outdated
Show resolved
Hide resolved
…o/opentelemetry/javaagent/instrumentation/netty/common/client/AbstractNettyHttpClientTracer.java Co-authored-by: Mateusz Rzeszutek <mrzeszutek@splunk.com>
trask
changed the title
trask
changed the title
trask
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pr removes netty 4.0 & 4.1
ChannelFutureListenerInstrumentationwhich was responsible for creating connection failure span and instead usesFutureListenerWrappersfor the same purpose. The reason behind this is that instrumentations using a matcher likeimplementsInterface(named("io.netty.channel.ChannelFutureListener"))don't apply to lambdas. For vert.x 4 the listener we want to intercept happens to be a lambda.