[
https://issues.apache.org/jira/browse/AMQ-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5614.
-----------------------------
Resolution: Fixed
DeadLetterStrategies now support expiration attribute, milliseconds till
expiry. Defaults to 0.
In case of a loop, like setting expiration on a shared strategy enabled as a
default, the audit will reject the duplicates.
Best used selectively with individual dead letter strategies and per
destination policies.
http://git-wip-us.apache.org/repos/asf/activemq/commit/0142c4dc
> Support message expiration in DLQ
> ---------------------------------
>
> Key: AMQ-5614
> URL: https://issues.apache.org/jira/browse/AMQ-5614
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.11.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.12.0
>
>
> Currently messages in the DLQ don't expire. With the option to expire, only
> timely messages remain and can be processes.
> Immediate expiry today can be achieved on a per destination basis with the
> discarding strategy of with the discarding dlq broker plugin.
> Using message expiry is a little more intuitive and more useful, because
> stale messages will be auto removed from the ops radar and timely messages
> can be dealt with as appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
