[ https://issues.apache.org/jira/browse/ARTEMIS-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447652#comment-16447652 ]
Lionel Cons commented on ARTEMIS-1794: -------------------------------------- [~jbertram] In the use case described here, {{/topic/foo}} and {{/queue/foo}} are not related at all. They see disjoint sets of messages. > Confusion when auto removing a queue > ------------------------------------ > > Key: ARTEMIS-1794 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1794 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: STOMP > Affects Versions: 2.5.0 > Reporter: Lionel Cons > Priority: Major > > I'm using the following settings to try to mimic ActiveMQ 5 STOMP destination > handling: > {code} > <acceptor > name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true;anycastPrefix=/queue/;multicastPrefix=/topic/</acceptor> > {code} > This works as expected in most situations. > However, when subscribing to a queue (via {{destination:/queue/foo}}) and > sending a message to an eponymous topic ({{destination:/topic/foo}}) Artemis > reports a fatal error: > {code} > AMQ119209 Can't remove routing type ANYCAST, queues exists for address foo. > Please delete queues before removing this routing type. > {code} > I guess this happens when it tries to auto delete things. > Doing the opposite (subscribing to the queue and sending a message to the > topic), I get the same kind of error: > {code} > AMQ119209 Can't remove routing type MULTICAST, queues exists for address foo. > Please delete queues before removing this routing type. > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)