[
https://issues.apache.org/jira/browse/ARTEMIS-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661833#comment-16661833
]
ASF GitHub Bot commented on ARTEMIS-1856:
-----------------------------------------
Github user michaelandrepearce commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2388#discussion_r227665143
--- Diff:
artemis-server/src/main/resources/schema/artemis-configuration.xsd ---
@@ -336,6 +336,14 @@
</xsd:annotation>
</xsd:element>
+ <xsd:element name="address-queue-scan-period" type="xsd:long"
default="30000" maxOccurs="1" minOccurs="0">
--- End diff --
Can this be added to the artemis-configuration used for testing to keep as
much as possible the two in sync
> 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
> Priority: Major
>
> 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)
