Make sure NettyDispatcher gets initialized #148
Merged
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
jack-berg
approved these changes
Dec 11, 2020
| @@ -26,12 +27,14 @@ | |||
| public class NettyDispatcher { | |||
|
|
|||
| private static volatile NettyDispatcher instance = null; | |||
| public static volatile AtomicBoolean instrumented = new AtomicBoolean(false); | |||
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.
When testing the spring-webflux-5.3.1 changes, @jack-berg and I found that the initial Transaction created by Netty-4.0.8 instrumentation was never getting created. The issue is that AbstractServerBootstrap isn't always used, consequently never triggering the (re)instrumentation of NettyDispatcher::channelRead , which is the Transaction start poing