[ISSUE #9992] Fix remoting server netty server codec thread reuse problem #9993
+9
−9
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.
Which Issue(s) This PR Fixes
Fixes #9992
Brief Description
When creating NettyRemotingServer, if the serverNettyWorkerGroupEnable parameter is set to false, Netty’s codec and handshake will use Netty’s built-in thread pool. However, some other parts of this class still use the business-layer–created defaultEventExecutorGroup. In this case, Netty’s codec may behave abnormally.
How Did You Test This Change?