Handle Solace Acknowledgements on worker pool instead of event loop thread#95
Merged
SravanThotakura05 merged 3 commits intomainfrom Feb 9, 2026
Merged
Conversation
ozangunalp
requested changes
Feb 2, 2026
Collaborator
Author
Thanks @ozangunalp for reviewing the change. I have added the suggested change |
ozangunalp
approved these changes
Feb 2, 2026
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
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.
An intermittent issue is observed where Solace message processing is stuck during OAuth token refresh. The analysis indicated a possible circular wait loop between reconnection and pending acknowledgements. This is causing a deadlock and failure as event loop thread is blocked for more than 2000ms.
As part of this pull request, Solace ack handling is moved to worker pool instead of event loop to prevent the deadlock