Cleanup the local cache of redis connections after closing them #13122
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
gsmet
added
the
triage/waiting-for-ci
|
Thanks! I included this change in 1.9.2.Final I'm going to release today. |
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.
The Redis extension crashes when using quarkus-dev after a hot reload. While it correctly closes all connections on shutdown, it forgets to clear the cache of reused redis connections. But since they are already closed, all calls from the new hot-reloaded application will fail with a
java.lang.IllegalStateException: Client is closed.The quick fix is to delete all
RedisAPIContainerinstances after closing them.