-
Notifications
You must be signed in to change notification settings - Fork 1.1k
GH-3716: Fix wait for init redisMessageListenerContainer #3719
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think just one our
isRunningRedisMessageListenerContainer
is enough.The problem is really that
RedisMessageListenerContainer
setsrunning = true;
in the beginning ofstart()
.Better to have it in the end, when subscription is ready.
But still we need that
synchronized (RedisLockRegistry.this.redisMessageListenerContainer)
anyway to block any concurrent calls for thestart()
.WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with what you said.
However, it was thought that it would be difficult to change that part in spring-integration, so I modified the code to handle it.
The reason to check both is because there is a code that sets
running = false;
(
isRunningRedisMessageListenerContainer
andredisMessageListenerContainer.isRunning()
)when an error occurs in
redisMessageListenerContainer.start()
, but will be not threw Exception.(https://github.com/spring-projects/spring-data-redis/blob/main/src/main/java/org/springframework/data/redis/listener/RedisMessageListenerContainer.java#L222)
There is almost no failure, but if it fails, it looks like we will have to run
start()
again, so I'm checking both.