Thorsten Kunz created ARTEMIS-3236:
--------------------------------------
Summary: broker.xml defined queue deleted on MQTT client
disconnect with auto-delete-created-queues=false
Key: ARTEMIS-3236
URL: https://issues.apache.org/jira/browse/ARTEMIS-3236
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.17.0
Environment: Artemis 1.17.0 on OpenJDK11
Reporter: Thorsten Kunz
If have the following address configuration in my broker.xml
{code:java}
<address name="COMMONNOTIFICATIONS.SMS">
<multicast>
<queue name="mqtt-client1.COMMONNOTIFICATIONS.SMS"/>
<queue name="mqtt-client2.COMMONNOTIFICATIONS.SMS"/>
</multicast>
</address>{code}
With the following address configuration for match="#" and no more specific
configs
{code:java}
<auto-create-queues>false</auto-create-queues>
<auto-delete-queues>true</auto-delete-queues>
<auto-delete-created-queues>false</auto-delete-created-queues>{code}
So since the queues are not auto-created but statically in the configuration I
would expect the queue to survive the client disconnect even if it doesn't
contain any messages.
But the observed behaviour is that the client can connect after the broker is
started and if the client disconnects the queue is gone so that when the client
reconnects it gets an error message that the queue is not there anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
