You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Johan Stenberg (JIRA)" <ji...@apache.org> on 2018/01/05 12:58:00 UTC
[jira] [Updated] (ARTEMIS-1584) Automatic Purging/Expiration of
messages in DLQ / Expiry Queue after predefined time span
[ https://issues.apache.org/jira/browse/ARTEMIS-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Stenberg updated ARTEMIS-1584:
------------------------------------
Summary: Automatic Purging/Expiration of messages in DLQ / Expiry Queue after predefined time span (was: Automatic Purging/Expiration of messages in DLQ / Expiry Queue)
> Automatic Purging/Expiration of messages in DLQ / Expiry Queue after predefined time span
> -----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1584
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1584
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Johan Stenberg
>
> DeadLetter/Expiry addresses rely on clients to consume messages. If for some reasons a client fails to do so, messages may get stuck in these queues forever. It would be great to be able to specify an action that is automatically performed after a message is put into an DLQ/expiry queue and not consumed within a given time, e.g. moving to another expiry address or discarding of the message.
> Something like http://activemq.apache.org/message-redelivery-and-dlq-handling.html#MessageRedeliveryandDLQHandling-SettingExpirationonMessagesintheDLQ but not limited to DLQs also for expiry addresses.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)