[
https://issues.apache.org/jira/browse/ARTEMIS-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648252#comment-16648252
]
Justin Bertram commented on ARTEMIS-2124:
-----------------------------------------
At this point I'd say you're seeing the expected behavior, and I'll explain
why...
The current implementation auto-deletes queues when the consumer-count of the
queue hits 0 and the message-count is also 0. There is a callback each time a
consumer is closed to check if the queue should be auto-deleted.
In your use-case there is a queue on broker A which is auto-created when a
message is sent to the eponymous address by a JMS producer using a JMS queue
(which uses anycast semantics). The same address and queue are auto-created on
broker B when a JMS consumer connects. The message in the queue on broker A is
then *redistributed* to the queue on broker B for the consumer to receive.
Technically speaking, there is no consumer on the queue on broker A which is
why the queue is not automatically deleted since the queue is only ever
automatically deleted when the last consumer is closed and the message-count is
0.
In any event, the existence of an auto-created queue whose consumer-count &
message-count are both 0 shouldn't have any real impact.
> Addresses/Queues are not auto-deleted in clusters
> -------------------------------------------------
>
> Key: ARTEMIS-2124
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2124
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.3
> Reporter: Johan Stenberg
> Priority: Major
> Attachments: Artemis2124_AutoDeleteTest.java
>
>
> All addresses and queues in one of our production cluster environment are
> configured as auto create/delete addresses and queues, however non of the
> addresses and queues are never seem to get auto-deleted.
> I am attaching a test case that I believe reproduces the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
