Ensure multiple consumer follows same processing logic as normal consumer #388
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.
Currently
MultipleConsumer
does not handle exceptions in the same way as the regularConsumer
since it uses its ownprocessQueueMessage
instead ofprocessMessage
, which does not include handlers for exceptions likeStopConsumerException
.I think that the
MultipleConsumer
should probably have the same behaviour for these exceptions, so I've placed the relevant code inprocessMessageQueueCallback
(I'm open to a better name for this) which is called byprocessMessage
inConsumer
andprocessQueueMessage
inMultipleConsumer
. This way when new functionality is added, both consumers should continue to have the same behaviour.