[
https://issues.apache.org/jira/browse/AMQ-9217?focusedWorklogId=844118&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-844118
]
ASF GitHub Bot logged work on AMQ-9217:
---------------------------------------
Author: ASF GitHub Bot
Created on: 07/Feb/23 13:27
Start Date: 07/Feb/23 13:27
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #965:
URL: https://github.com/apache/activemq/pull/965#issuecomment-1420776857
> I don't think a flag is what we should do. For me, it sounds more like a
bug, so just changing the default behavior is OK.
Yeah this probably makes the most sense, it would be a behavior change but
the current behavior just seems broken and a bug so might as well change it for
the individual strategy. Anytime we add flags 99% of the time no one is going
to change the default so we should just fix it I think unless someone can think
of a good reason not to change it.
Issue Time Tracking
-------------------
Worklog Id: (was: 844118)
Time Spent: 0.5h (was: 20m)
> Add config flag to support per-destination audit in AbstractDeadLetterStrategy
> ------------------------------------------------------------------------------
>
> Key: AMQ-9217
> URL: https://issues.apache.org/jira/browse/AMQ-9217
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 5.18.0, 5.17.4
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> By default, dead letter strategies are shared per destination policy. This
> breaks for IndividualDeadLetterStrategy destination policies, where if the
> same message is DLQ'd from two queues (ie. Virtual Destination forwarding),
> only one message will be permitted to DLQ.
> A flag to enable a fix for this in 5.17.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
