fix: prevent WebsocketSyncDataService from shutting down shared timer (#6785) - #6982
Merged
Merged
Conversation
…ss, and lifecycle management
Aias00
approved these changes
Aug 26, 2026
Aias00
left a comment
Aias00
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the changes and did not find blocking issues.
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.
What this PR does
WebsocketSyncDataService.HierarchicalWheelTimerterminates its worker thread correctly on shutdown.Why
WebsocketSyncDataService.close()previously shut down the shared timer obtained fromWheelTimerFactory.getSharedTimer(). This could break other components using the same timer, such asFailbackRegistryRepository.Closes #6785.
@Aias00, could you please help review this PR? Thank you!