Add a per-bean-name lock around destroy/reset/re-populate/re-initialize steps in rebind - #1721
Merged
ryanjbaxter merged 1 commit intoAug 10, 2026
Conversation
…ze steps in rebind
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
1 participant
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.
Fixes part of the issues originally reported in #1709
ConfigurationPropertiesRebinder had no synchronization at all, so two threads rebinding the same bean at the same time (for example a manual /actuator/refresh racing a config-watch-triggered refresh) could interleave their destroy/reset/re-populate/re-initialize steps on top of each other.
This adds a per-bean-name lock around that sequence in rebind(String, ApplicationContext), so concurrent rebinds of the same bean are now serialized instead of interleaved.