[
https://issues.apache.org/jira/browse/ARTEMIS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342330#comment-15342330
]
Justin Bertram commented on ARTEMIS-582:
----------------------------------------
Couple of things...
* There's no need to know any internals of Artemis or ActiveMQ for simple
comparative analysis. All that's necessary is a standardized test used for
both brokers and a way to measure the results which could be as simple as
watching the memory graph in VisualVM or JConsole.
* Artemis implements OpenWire so it should (theoretically) be backward
compatible. Although looking more closely at MCollective it appears it's using
STOMP which will almost certainly suffer some incompatibilities between brokers.
* The documentation I cited previously describes when an auto-create queue or
topic will be deleted.
* Can you provide a simple test to reproduce what you're seeing? I wrote a
quick test in the Artemis test-suite to ensure that auto-created queues are
deleted as expected and it passed without issue.
> 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)
