Fixes #569: NoSuchElementException in Session.drainQueueToConnection #570
Conversation
This file contains 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
…Connection Session.drainQueueToConnection checks sessionQueue.isEmpty(), and then uses sessionQueue.remove(). However, between the check and the remove, another thread can steal the last message, causing the remove() to throw an exception. Better to use sessionQueue.poll() with a null-check.
This was referenced Feb 3, 2021
andsel
approved these changes
May 1, 2021
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.
Session.drainQueueToConnection checks sessionQueue.isEmpty(), and then
uses sessionQueue.remove(). However, between the check and the remove,
another thread can steal the last message, causing the remove() to throw
an exception. Better to use sessionQueue.poll() with a null-check.