SyncResponseHandlerAdapter: Prevent overflow #1542
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.
SyncResponseHandlerAdapter requests
Long.MAX_VALUE
from itsPublisher
, not just initially upon subscription but also on every#onNext
call. This means that everySubscription
implementation thatdoes not take steps to prevent overflow (or which throws an exception if
overflow is detected) will eventually see the number of outstanding
requests go negative, and will stop consuming data. Larger responses
require more calls to
#onNext
and are therefore more likely toencounter this issue.
The fix is simply to request new messages individually, so that the
number of outstanding requests always hovers around
Long.MAX_VALUE
.I confirm that this pull request can be released under the Apache 2 license.