You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2021/12/15 13:59:00 UTC

[jira] [Closed] (ARTEMIS-3529) Expire move should not reject duplicates from duplicateID

     [ https://issues.apache.org/jira/browse/ARTEMIS-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-3529.
------------------------------------

> Expire move should not reject duplicates from duplicateID
> ---------------------------------------------------------
>
>                 Key: ARTEMIS-3529
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3529
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>            Priority: Major
>             Fix For: 2.20.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The issue is that duplicateID makes sense with client to server.. and the move should ignore it.
> You could have two independent queues with the same ID from each one, and the move should still succeed.
> Also, the message could be retried and a second retry should not test duplicate reject again.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)