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

Lionel Cons commented on ARTEMIS-1932:
--------------------------------------

So if one consumer subscribes to a wildcard destination and then later 
unsubscribes, then the new messages will still pile up forever in this wildcard 
queue that has just been used once.

This is IMHO error prone and AFAIK this is different from what ActiveMQ 5.x 
does.

Note that the auto delete setting only partially helps. If a message is 
received while the client unsubscribes then the queue will not be empty and 
therefore will not be deleted.

I have the feeling that the wildcard subscriptions, just like the topic 
subscriptions, should be temporary and should be destroyed when the client 
unsubscribes, regardless of the auto delete setting.

> Wildcard subscriptions create permanent bindings (STOMP)
> --------------------------------------------------------
>
>                 Key: ARTEMIS-1932
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1932
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Lionel Cons
>            Priority: Major
>         Attachments: ARTEMIS-1932.text, broker.xml
>
>
> When using STOMP to create a wildcard subscription to {{/queue/test.\*}}, 
> Artemis creates a {{/queue/test.\*}} address and an eponymous ANYCAST queue 
> within. So far, so good.
> However, these automatically created objects are permanent and survive at the 
> end of the connection.
> Here is the test scenario:
>  - start with an empty broker
>  - connect
>  - subscribe to {{/queue/test.\*}}
>  - unsubscribe
>  - disconnect
>  - bug => the address and queue remain
>  - connect
>  - send a message to {{/queue/test.foo}}
>  - bug => the message appears in the {{/queue/test.\*}} queue (in addition to 
> {{/queue/test.foo}})
> FWIW, I'm using {{default-address-routing-type}} to make sure destinations 
> starting with {{/queue/}} act like a queue (see ARTEMIS-1906).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to