[FIXED] Publish async not closing done and stall channels after failed retries #1719
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
…d retries This fixes an issue in new JetStream API where if maximum number of retries in `PublishMsgAsync` are reached and the publish failed, done and stall channels are not closed. Additionally, this fixes a potential race issue with modifying user msg when publishing. Signed-off-by: Piotr Piotrowski <piotr@synadia.com>
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.
This fixes an issue in new JetStream API where if maximum number of retries
in
PublishMsgAsyncare reached and the publish failed, done and stall channelsare not closed.
Additionally, this fixes a potential race issue with modifying user msg when publishing.
Signed-off-by: Piotr Piotrowski piotr@synadia.com