Github user mtaylor commented on the issue: https://github.com/apache/activemq-artemis/pull/2392 > > With AMQP raw, there is no such thing as a routing type (this is a broker concept). Therefore messages sent via AMQP to an address should be routed to any routing type currently configured on that address. If an address has a single routing type configured e.g. Multicast, the message should be routed there, it should not create a new routing type with Anycast, which is what is happening here. > > agreed > > > Artemis also implements the JMS AMQP extension, which enables additional functionality, one of which is the ability to define a sender destination type, i.e. Queue or Topic. These map to Address Anycast and Multicast respectively. In this case (with auto-create disabled), if an AMQP client using this extension e.g. QPID JMS client, sends explicitly sends to Anycast, but only a Multicast address exists, then an error should be returned. > > With auto-create enabled for both addresses and queues, the behaviour would be different, an Anycast address would be created and no error thrown. > > This would make sense if anycast and multicast addresses (i.e. queue and topic) were entirely independent. They are not though. I am not sure what you mean by entirely independent. Can you elaborate.
---