[
https://issues.apache.org/jira/browse/ARTEMIS-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155015#comment-17155015
]
Justin Bertram commented on ARTEMIS-2841:
-----------------------------------------
This may have been closed by mistake as part of the 2.14.0 release process.
In any event, I think some of what you want is already possible using the
{{expiry-delay}} address setting. Using this setting the broker can apply a
TTL/expiry delay on any incoming message that doesn't already have a TTL/expiry
value set. There's also the {{min-expiry-delay}} and {{max-expiry-delay}} which
you can use to change the value of the TTL/expiry delay on messages which
already have one set. Read more about this in [the
documentation|http://activemq.apache.org/components/artemis/documentation/latest/message-expiry.html].
That said, there is no option to set an absolute expiration time (e.g. all
messages expire at midnight).
> Global TTL and/or exact xxpiry time for a broker/address
> --------------------------------------------------------
>
> Key: ARTEMIS-2841
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2841
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.14.0
> Reporter: obby
> Priority: Major
> Labels: features
> Fix For: 2.15.0
>
>
> In certain application logic and business requirements I have come across,
> there has been a need to have a global TTL or set time for expiry of all
> messages in a broker or address. one use case was that at midnight, all
> messages should expire and not be sent. Another use case was that every
> message would have a set ttl (8 hours). This is all achievable currently from
> application by setting the expiry time or expiration delay for a message in
> the the producer. But it would really be helpful if there was an option to
> set the same at address/broker level.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
