reuse rabbitMQ connection and channel #27
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
|
Amazing, thank you! |
aznamier
pushed a commit
that referenced
this pull request
Nov 9, 2022
dcherix
added a commit
to dcherix/keycloak-event-listener-rabbitmq
that referenced
this pull request
May 4, 2023
# Conflicts: # src/main/java/com/github/aznamier/keycloak/event/provider/RabbitMqEventListenerProvider.java
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.
Problem:
Our rabbitMQ cluster is experiencing issues probably due to too many and too frequent user connections.
Solution:
Reuse the connection and channel of the rabbitMQ client to avoid to have to connect on every event.