[
https://issues.apache.org/jira/browse/ARTEMIS-3529?focusedWorklogId=665434&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-665434
]
ASF GitHub Bot logged work on ARTEMIS-3529:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Oct/21 23:11
Start Date: 13/Oct/21 23:11
Worklog Time Spent: 10m
Work Description: clebertsuconic merged pull request #3793:
URL: https://github.com/apache/activemq-artemis/pull/3793
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 665434)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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.3.4#803005)
