You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2020/04/16 22:48:02 UTC

[jira] [Closed] (ARTEMIS-2701) Update delivery / DLQ check to be resilient to record not existent

     [ https://issues.apache.org/jira/browse/ARTEMIS-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-2701.
------------------------------------
    Resolution: Fixed

> 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: 1h
>  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)