[
https://issues.apache.org/jira/browse/AMQ-9217?focusedWorklogId=844468&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-844468
]
ASF GitHub Bot logged work on AMQ-9217:
---------------------------------------
Author: ASF GitHub Bot
Created on: 08/Feb/23 21:58
Start Date: 08/Feb/23 21:58
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #965:
URL: https://github.com/apache/activemq/pull/965#issuecomment-1423292639
I should add a quick note that I merged this but this doesn't solve all
issues (but makes things much better). It uses the original destination and not
the DLQ destination the message is going to which means that in some cases
(like if destinationPerDurableSubscriber flag is true) a copy of the message
for each destination still wouldn't be DLQ'd as more than one destination still
shares a message audit. So while this greatly improves things it isn't perfect.
A follow in issue/PR can be created to improve it further if desired to handle
the more complex cases.
Issue Time Tracking
-------------------
Worklog Id: (was: 844468)
Time Spent: 2h 10m (was: 2h)
> 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: 2h 10m
> 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)
