Message selectors and enable auto-reconnect#12
Open
wumbrath wants to merge 18 commits into
Open
Conversation
- in case of a message ack failure we do a recovery. this is need in particular for auto reconnect scenarios after a broker is restarted
- poisoned message protection
- messages resulting in null tuples are not emitted but acknowledged
- non-blocking receive
* check batch on ack/fail
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
2 participants
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.
Patch includes support for jms message selectors.
Additionally in case of a message ack failure we do a recovery. This is needed in particular for auto reconnect scenarios in conventional clusters after a broker is restarted. In such a case no ack is accepted unless a recovery is performed.