[jira] [Resolved] (ARTEMIS-1856) Add support for delays before deleting addresses and queues

["Justin Bertram (JIRA)" <ji...@apache.org>]

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

Justin Bertram resolved ARTEMIS-1856.
-------------------------------------
       Resolution: Fixed
         Assignee: Justin Bertram
    Fix Version/s: 2.7.0

> Add support for delays before deleting addresses and queues
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-1856
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1856
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Lionel Cons
>            Assignee: Justin Bertram
>            Priority: Major
>             Fix For: 2.7.0
>
>
> By default, Artemis deletes inactive addresses and empty queues. This is good to minimize the resources used.
> However, this is problematic for monitoring because counters (like the numbers of received and sent messages) are attached to these objects that get deleted. So a monitoring tool periodically probing the broker may miss these objects that get immediately deleted.
> It would be good to add support for delays. An object would not be immediately deleted but would stay in the broker for a configurable period of time, so that monitoring tools get a chance to get its counters.
> Note that this feature (delayed deletion) already exists in ActiveMQ 5. See the {{gcInactiveDestinations}}, {{schedulePeriodForDestinationPurge}} and {{inactiveTimoutBeforeGC}} parameters in http://activemq.apache.org/delete-inactive-destinations.html.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)