fix(rabbitmq): use shared Netty EventLoopGroup to prevent resource leaks and shutdown issues#163
Merged
juancgalvis merged 3 commits intoreactive-commons:masterfrom Jan 28, 2026
Conversation
…y EventLoopGroup lifecycle
luisgomez29
changed the title
luisgomez29
changed the title
juancgalvis
approved these changes
Jan 28, 2026
Contributor
|
🎉 This PR is included in version 7.0.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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.
Description
This PR resolves the recurring logs
"Could not close event loop group in 10 seconds"when using RabbitMQ with Netty, following the official recommendations from the RabbitMQ documentation.Changes
EventLoopGroupfor all RabbitMQ connections, avoiding the creation of multiple thread groups and improving efficiency.MultiThreadIoEventLoopGroupandNioIoHandler.newFactory()), allowing Netty to automatically determine the optimal number of threads.