At closing consumer: make pendingRead false when no consumer is connected to SingleDispatcher #60
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.
Motivation
In case of
Exclusive
consumer is disconnecting and if it doesn't fliphavePendingRead=false
at PersistentDispatcherSingleActiveConsumer, then on next reconnection consumer will not receive new messages and it will be blocked.So, we should make
havePendingRead=false
at the time of disconnect-consumer if there is no consumer availableExclusive
subscription: ifhavePendingRead=true
andcursor.cancelPendingReadRequest()=false (which will be the case if there is no pendingReadOp present at ManagedCursor)
,havePendingRead
will be always true and next time when new consumer will connect, it might get blocked at pickAndScheduleActiveConsumer while addConsumer() and at consumerFlowModifications
Always clear pendingRead at Exclusive consumer disconnect.
Result
Avoid possibility of exclusive consumer blocking.