[
https://issues.apache.org/activemq/browse/AMQ-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63325#action_63325
]
Gary Tully commented on AMQ-3003:
---------------------------------
@Kurt, I have not, but if that is happening try implementing a custom
org.apache.activemq.broker.region.policy.DeadLetterStrategy and you should have
the option to fix it up or specify the DLQ destination name.
> Allow the option of a DLQ per durable subscription DeadLetterStrategy
> ---------------------------------------------------------------------
>
> Key: AMQ-3003
> URL: https://issues.apache.org/activemq/browse/AMQ-3003
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.4.1
> Reporter: Gary Tully
> Fix For: 5.5.0
>
>
> From https://issues.apache.org/activemq/browse/AMQ-2584 - with durable
> subscriptions sharing the DLQ there will be duplicate sends to the dlq if
> more than one durable sub rejects the message.
> These durables are suppressed provided they are not already acked, in which
> case the duplicate can hang about. The audit=false option for the DLQ works
> around this, but it begs the question, can I know which durable subscription
> refused a message.
> To facilitate this, having a DLQ pre durable sub is a nice option. It can use
> the clientId and subscriberName as the postfix, so
> ACTIVEMQ_DLQ.ClientId-SubscriberName - If the subscriber changes subsequent
> messages can go do a different DLQ. These destinations would need to be
> manually deleted when no longer needed.
> This will require additional methods in
> org.apache.activemq.broker.region.policy.DeadLetterStrategy so will need to a
> version update.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
