ActiveMQ Artemis was designed from the ground up to support multiple protocols. As such, it needs a flexible and powerful address model to support lots of different use cases across the wide variety of supported protocols. This flexibility can sometimes be confusing for users of STOMP which only defines a flat "destination" with no particular semantics. In general just remember that you send messages to an address and consume messages from a queue. When a message is sent to an address it is routed to the queues bound to that address.
For a STOMP client using auto-creation the "destination" header should have the same value for both producers and consumers. The broker will take care of the rest under the covers. In the case of publish-subscribe semantics the broker will create a queue for each subscription. You wouldn't normally configure this queue statically in broker.xml, although you could if you really wanted to for some reason (again, the model is flexible). I hope that helps. Justin On Tue, Aug 11, 2020 at 12:16 PM Christopher Pisz <christopherp...@gmail.com> wrote: > I read that an address can have many queues. I am not sure what an address > really is otherwise. I only have one field in my stomp messages that I can > specify, and it is labeled "destination", is that the address name or the > queue name? > > How would I even specify the other? > > Or does Artemis create a queue per subscription? If so, then why would you > put anything in the config for it, because you don't know the subscription > will exist until it is made. > > I am confused. >
