You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2021/09/30 14:10:00 UTC

[jira] [Resolved] (ARTEMIS-1583) Allow broker-side specification of max TTL for messages

     [ https://issues.apache.org/jira/browse/ARTEMIS-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-1583.
-------------------------------------
    Resolution: Duplicate

> Allow broker-side specification of max TTL for messages
> -------------------------------------------------------
>
>                 Key: ARTEMIS-1583
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1583
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Johan Stenberg
>            Priority: Major
>
> We have the requirement that in some queues messages should only be hold for a given amount of time, no matter if the client specified a longer TTL for a message. In rabbit-mq this can be realized using message policies [https://www.rabbitmq.com/ttl.html], maybe the AddressSettings are a good place to specify a max message TTL.
>  
> For ActiveMQ5 exists the [http://activemq.apache.org/timestampplugin.html] which one can use to achieve similar but since it always seems to modify a message's timestamp which is problematic in regards to JMS spec and the fact that AMQP 1.0 messages are immutable per spec.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)