fix #2376 - avoid deadlock scenario when completing dead connections #2378
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.
Deadlock scenario reported with one path (
RecordConnectionFailed
) taking queue then message locks, and another path (ExecuteSyncImpl
) taking message then queue locks; change both paths to only take one lock at a time - never nested.RecordConnectionFailed
don't hold the queue lock when we abort things - only hold it when fetching nextExecuteSyncImpl
, don't hold the message lock when throwing for timeoutGetHeadMessages
, don't blindly wait forever on the message lockalso standardise on
TryPeek
/TryDequeue