Fix maxMessagesPerPoll for SourcePollingChAdapter #8747
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.
The
AbstractMethodAnnotationPostProcessor
does not check forPollerMetadata.MAX_MESSAGES_UNBOUNDED
before settingmaxMessagesPerPoll
into aSourcePollingChannelAdapter
which in this case must be1
Also fix
SourcePollingChannelAdapterFactoryBean
to not mutate the providedPollerMetadata
(which might be global default) with a newmaxMessagesPerPoll
Cherry-pick to
6.1.x
&6.0.x