[
https://issues.apache.org/jira/browse/ARTEMIS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339817#comment-15339817
]
Justin Bertram commented on ARTEMIS-582:
----------------------------------------
Couple of questions:
* The cited MCollective documentation indicates that orphaned single-use queues
will "clog up ActiveMQ’s available memory." Can you confirm that the behavior
here in Artemis is similar to that of ActiveMQ 5.x? In other words, do
orphaned single-use queues clog up Artemis' available memory? If so, can you
quantify the clogging (e.g. X number of orphaned single-use queues in Y bytes
of heap causes high GC or OOME)?
* Artemis supports the automatic deletion of JMS queues (see [the
docs|http://activemq.apache.org/artemis/docs/1.3.0/queue-attributes.html] for
more details on that). Can MCollective be configured to use JMS queues rather
than core queues for the single-use queues that it needs?
> Add support for automatic deletion of unused destinations
> ---------------------------------------------------------
>
> Key: ARTEMIS-582
> URL: https://issues.apache.org/jira/browse/ARTEMIS-582
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Lionel Cons
>
> ActiveMQ 5.x can be configured to automatically delete inactive destinations,
> see http://activemq.apache.org/delete-inactive-destinations.html.
> This is very useful for clients that create short-live reply destinations,
> like MCollective does (see
> https://docs.puppet.com/mcollective/deploy/middleware/activemq.html#reply-queue-pruning).
> Could Artemis also be configured to automatically delete inactive
> destinations?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
