[
https://issues.apache.org/jira/browse/ARTEMIS-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481187#comment-17481187
]
ASF subversion and git services commented on ARTEMIS-3529:
----------------------------------------------------------
Commit 8abff60ac5af353f519f5b7f39e495305539504a in activemq-artemis's branch
refs/heads/2.19.x from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=8abff60 ]
ARTEMIS-3529 Tweaks on test - Removing AssertionLogger and reformat
(cherry picked from commit fd122094888e905a7d1e4e05e6c617a51290aa74)
> 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, 2.19.1
>
> 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)
