[ 
https://issues.apache.org/jira/browse/ARTEMIS-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351183#comment-17351183
 ] 

ASF subversion and git services commented on ARTEMIS-3236:
----------------------------------------------------------

Commit 6ec7a69d45d2aad2222f444104de2824d83c929f in activemq-artemis's branch 
refs/heads/main from Domenico Francesco Bruscino
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6ec7a69 ]

ARTEMIS-3236 Preserve managed queues on removing MQTT subscription


> 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 2.17.0 on OpenJDK11
>            Reporter: Thorsten Kunz
>            Assignee: Domenico Francesco Bruscino
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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)

Reply via email to