activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3003) Allow the option of a DLQ per durable subscription DeadLetterStrategy
Date Mon, 21 Mar 2011 23:47:05 GMT


Gary Tully resolved AMQ-3003.

    Resolution: Fixed
      Assignee: Gary Tully

implemented in

new boolean attribute 'destinationPerDurableSubscriber' on IndividualDeadLetterStrategy that
will prepend the durable subscription key to the individual dlq destination.
Added message and subscription to the DeadLetterStrategy such that finer level control over
the DLQ destinations is possible through a custom strategy.
Note: Broker and DeadLetterStrategy interfaces changes.

> Allow the option of a DLQ per durable subscription DeadLetterStrategy
> ---------------------------------------------------------------------
>                 Key: AMQ-3003
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.4.1
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.5.0
> From - 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
so will need to a version update.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message