FELIX-6844: Implement self-healing recovery mechanism for FelixDispatchQueue thread in EventDispatcher#506
Open
sahvx655-wq wants to merge 2 commits into
Open
Conversation
Author
|
CI is failing due to AssertJ version range mismatch: required [3.27.3,3.27.4) but 3.27.7 is available in the resolver. Should the range be widened in tck.bndrun? |
sahvx655-wq
force-pushed
the
event-dispatcher-self-healing
branch
from
5a3e07e to
6fdaae4
Compare
sahvx655-wq
changed the title
added 2 commits
June 17, 2026 20:13
…chQueue thread in EventDispatcher
sahvx655-wq
force-pushed
the
event-dispatcher-self-healing
branch
from
6fdaae4 to
fb331ac
Compare
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.
This PR introduces a controlled self-healing mechanism for the FelixDispatchQueue thread in EventDispatcher to prevent permanent asynchronous event failure when the dispatcher thread crashes due to severe runtime errors (e.g., OutOfMemoryError, StackOverflowError).
Currently, if the dispatcher thread dies, the framework permanently stops processing asynchronous events. This change adds a safe recovery strategy while preserving the existing single-threaded design.