You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/10/13 23:12:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17428528#comment-17428528 ]
ASF subversion and git services commented on ARTEMIS-3529:
----------------------------------------------------------
Commit 1d84800d5a90d250851f7b3939650772776c0ae7 in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1d84800 ]
ARTEMIS-3529 Expire should not reject messages from duplicateID
> 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
>
>
> 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.3.4#803005)