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 2025/05/24 03:11:00 UTC

[jira] [Resolved] (ARTEMIS-2119) Support custom expiry-delay at queue level

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

Justin Bertram resolved ARTEMIS-2119.
-------------------------------------
    Resolution: Won't Do

I don't see a compelling use-case for this so I'm closing. Feel free to re-open with additional justification.

> Support custom expiry-delay at queue level
> ------------------------------------------
>
>                 Key: ARTEMIS-2119
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2119
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Michael Andre Pearce
>            Priority: Major
>
> Currently the broker can set message expiry if not set by client, though this is implemented at the address setting and address level only, as such affects all queues beneath.
> To be more flexible it would be good to being able to set this default expiry delay at the queue level.
> Also it would be good to be able to set an enforced max-expiry-delay and min-expiry-delay, similar in nature to qpid
> [http://qpid.apache.org/releases/qpid-broker-j-7.0.1/book/Java-Broker-Concepts-Queues.html#d0e1051]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact