Potential deadlock in matchAndDispatch #470
Merged
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
MattBrittan
added a commit
to ChIoT-Tech/paho.mqtt.golang
that referenced
this pull request
Dec 21, 2020
This issue was picked up when running the tests multiple times (seemed to happen 1/10 ot the time)
MattBrittan
added a commit
that referenced
this pull request
Dec 21, 2020
Resolve issue introduced in pull request #470 (missing continue).
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.
matchAndDispatchwas sending toclient.oboundPwhich created a potential deadlock (in rare situations). This change brings control of thematchAndDispatchlifecycle understopCommsWorkers(removes the use of theclient.outboundpchannel) which should ensure a managed shutdown (with any outstandingACKmessages transmitted if possible).