[
https://issues.apache.org/jira/browse/ARTEMIS-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906781#comment-17906781
]
ASF subversion and git services commented on ARTEMIS-5215:
----------------------------------------------------------
Commit 6e969687427df10b4f1d3f51b68e08656034d04a in activemq-artemis's branch
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6e96968742 ]
ARTEMIS-5215 AMQP federation consumer close can allow duplicates on remote
Messages that are in-flight on a link when the federation consumer is closed
due to removal of local demand might get enqueued on the local broker but the
disposition might not get sent to the remote leading to a release of the message
back to the source queue leading to a duplicate being left on the remote. The
AMQP receiver links need to be drained and any pending settlements need to be
sent before the link can be allowed to be detached.
> AMQP Federation Queue Consumer can leave a duplicate message on remote broker
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-5215
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5215
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.39.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.40.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When local demand is removed from a federated Queue and the AMQP receiver is
> shutting down it needs to drain the link *and* await any pending settlements
> to be sent before detaching the link otherwise there is a window in which a
> message could be enqueued on the local broker but also released back to the
> queue on the remote leading to a duplicate.
--
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
