[
https://issues.apache.org/jira/browse/ARTEMIS-2701?focusedWorklogId=416708&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-416708
]
ASF GitHub Bot logged work on ARTEMIS-2701:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/20 15:53
Start Date: 06/Apr/20 15:53
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on issue #3067: ARTEMIS-2701
Improving DLQ/check over previously removed records
URL: https://github.com/apache/activemq-artemis/pull/3067#issuecomment-609879516
I added two operations to the journal...
tryUpdate
tryDelete
and used them on DLQ / Rollback
if something previously removed the message during the DLQ check.. we will
just ignore the operation normally.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 416708)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
