Fix exception handling for reactive consumers #455
Merged
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.
Version 4.1.0 introduced a bug for reactive consumers, the
DefaultKafkaListenerExceptionHandler
is always used even when a bean implements its ownKafkaListenerExceptionHandler
.The problem was introduced here #441, there are a couple of calls to the
handleException()
that expects aconsumerBean
which are receiving aconsumerState
. Added a test to verify that the simple fix works.cc @dstepanov