[
https://issues.apache.org/jira/browse/ARTEMIS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009321#comment-17009321
]
Adil Arif commented on ARTEMIS-2587:
------------------------------------
Thank you Justin for taking the time to respond back to the ticket. I have been
a huge fan of this project.
Based on the behavior that I see, ActiveMQ Artemis does allow messages that go
into a DLQ to use the two special unique properties. More so, with a wildcard
character under match attribute in an address settings, it is able to capture
DLQ messages from many queues. An admin can then then retry the DLQ messages
from Hawtio.
The use case that this approach doesn't support is where an enterprise can
establish a policy that enforces all JMS queues would have its own equivalent
DLQ without having to specify an address-setting for each of the queue. Any
queue that is created against a message broker would have its own DLQ created
by default. ActiveMQ Artemis currently doesn't provide this broker wide
enterprise policies.
The advantages of having this functionality is:
* More automation without requiring admin adding a special address-setting to
define a DLQ for each queue
* Ability for enterprise to implement standards and policies across the broker
* Messages that have failed in the JMS queue can be easily viewable and
located in its own DLQ
** This is advantageous for administrators as they don't have to sift through
a wildcard queue to view all failed messages related to a special queue
Do you feel this is a valid use case? Thank you!
> ActiveMQ5-like dead letter strategy
> -----------------------------------
>
> Key: ARTEMIS-2587
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2587
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Adil Arif
> Priority: Major
>
> In ActiveMQ 5 there is an {{individualDeadLetterStrategy}} policy available
> for the [Dead Letter
> Strategy|http://activemq.apache.org/message-redelivery-and-dlq-handling.html],
> e.g.:
> {noformat}
> <policyEntry queue=">">
> <deadLetterStrategy>
> <individualDeadLetterStrategy queuePrefix="DLQ."
> useQueueForQueueMessages="true"/>
> </deadLetterStrategy>
> </policyEntry>{noformat}
> This feature allows organizations to implement standardized policies on a
> broker for ensuring each queue has its own equivalent dead letter queue in an
> easy to configure fashion.
> This feature has shown interest by others in the past on the [mailing
> list|http://activemq.2283324.n4.nabble.com/Artemis-DLQ-strategy-td4710234.html]
> as well as [Red Hat's Knowledgebase
> |https://access.redhat.com/solutions/3140741].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
