[
https://issues.apache.org/jira/browse/ARTEMIS-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic closed ARTEMIS-5627.
------------------------------------
Resolution: Won't Fix
This could cause some corner cases...
if we ever bring this feature back we would need to treat AckReason for the
retry. we should only kick consumers on such feature if it was coming from
another consumer.
Another case where this could have issues is say you accumulate messages,
failover and retries are still happening... consumers would keep being
disconnected until the retry list is expired.
> Possibility of kicking of consumers on Mirror Target during ACK Retries
> -----------------------------------------------------------------------
>
> Key: ARTEMIS-5627
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5627
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> During an ACK retry on mirror, it is possible that consumers are still
> unexpectedly available in the mirror target. With this option the ACK Manager
> would kick consumers away opening the possibility of a proper ack retry.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
