You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2023/04/04 13:41:00 UTC
[jira] [Updated] (AMQ-9240) Enable queue/topic specific expiration configuration
[ https://issues.apache.org/jira/browse/AMQ-9240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Pavlovich updated AMQ-9240:
--------------------------------
Fix Version/s: 5.19.0
> Enable queue/topic specific expiration configuration
> ----------------------------------------------------
>
> Key: AMQ-9240
> URL: https://issues.apache.org/jira/browse/AMQ-9240
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.18.0
> Reporter: Ephemeris Lappis
> Priority: Major
> Labels: activemq, config.xml, configuration
> Fix For: 5.19.0
>
>
> The ActiveMQ "classic" version supports [TimeStamp PlugIn|[https://activemq.apache.org/timestampplugin]] to force expiration (attribute {_}zeroExpirationOverride{_}) for messages at the broker scope.
> It should be useful to have a similar option to force expiration at the queue/topic level, for example in the policy entries where it's already possible to configure DLQ strategies and so on for selected queues or topics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)