You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2022/01/17 10:19:00 UTC
[jira] [Comment Edited] (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=17477092#comment-17477092 ]
Robbie Gemmell edited comment on ARTEMIS-3529 at 1/17/22, 10:18 AM:
--------------------------------------------------------------------
For later reference, I think the last 3 related commits above should have been referenced against ARTEMIS-3461 rather than this JIRA, i.e:
https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6bb4aa7
https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=54418df
https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1db3ae1
was (Author: gemmellr):
For later reference, I think the last 3 related commits above should have been referenced against ARTEMIS-3529 rather than this JIRA, i.e:
https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6bb4aa7
https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=54418df
https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1db3ae1
> 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)