[
https://issues.apache.org/jira/browse/ARTEMIS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-2726.
-------------------------------------
Fix Version/s: 2.13.0
Resolution: Fixed
> Implement min/max expiry-delay
> ------------------------------
>
> Key: ARTEMIS-2726
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2726
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 2.12.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.13.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At present, the {{address-setting}} {{expiry-delay}} allows setting an
> expiration on a message if one is not already set. However, being able to
> enforce a _range_ would be useful.
> Example:
> {code:xml}
> <address-setting match="myAddress">
> <min-expiry-delay>10</min-expiry-delay>
> <max-expiry-delay>100</max-expiry-delay>
> </address-setting>
> {code}
> Semantics could be as follows:
> * Messages _without_ an expiration will be set to {{max-expiry-delay}}. If
> {{max-expiry-delay}} is not defined then the message will be set to
> {{min-expiry-delay}}. If {{min-expiry-delay}} is not defined then the message
> will not be changed.
> * Messages with an expiration _above_ {{max-expiry-delay}} will be set to
> {{max-expiry-delay}}
> * Messages with an expiration _below_ {{min-expiry-delay}} will be set to
> {{min-expiry-delay}}
> * Messages with an expiration _within_ {{min-expiry-delay}} and
> {{max-expiry-delay}} range will not be changed
> * Any value set for {{expiry-delay}} other than the default (i.e. {{-1}})
> will override the aforementioned min/max settings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
