[
https://issues.apache.org/jira/browse/ARTEMIS-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076483#comment-17076483
]
ASF subversion and git services commented on ARTEMIS-2701:
----------------------------------------------------------
Commit af796d5ce4129b9c0359d9868d434dadd3f30beb in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=af796d5 ]
ARTEMIS-2701 Improving DLQ/check over previously removed records
> Update delivery / DLQ check to be resilient to record not existent
> ------------------------------------------------------------------
>
> Key: ARTEMIS-2701
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2701
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.11.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When updating DLQ, it's possible that the queue was removed by another
> failing process.
> This is quite common on auto-created queues.
> In case it happens, the DLQ check should be resilient and just ignore such
> condition.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
