When clients connect to an address with the multicast element, a subscription queue for the client will be automatically automatically created for the client. It is also possible to pre-configure subscription queues and connect to them directly using the queue's Fully Qualified Queue names. Optionally add one or more queue elements are able to select the queue that they would like to subscribe to. Should more than one consumer connect directly to a single queue, Apache ActiveMQ Artemis will take care of distributing messages between

When clients connect to an address with the multicast element, a subscription queue for the client will be automatically automatically created for the client. It is also possible to pre-configure subscription queues and connect to them directly using the queue's Fully Qualified Queue names. Optionally add one or more queue elements are able to select the queue that they would like to subscribe to. Should more than one consumer connect directly to a single queue, Apache ActiveMQ Artemis will take care of distributing messages between

required. This saves you from having to preconfigure each address and queue before a client can connect to it. The broker can optionally be configured to automatically delete addresses and queues when queues and the broker will automatically create queues for each subscription when the consumers connect to address.foo . Then when a message is sent to address.foo it will be routed to each queue for there are scenarios where a user may want to statically configure a subscription queue and later connect to that queue directly using a Fully Qualified Queue Name (FQQN). Model 50 An FQQN uses a special

required. This saves you from having to preconfigure each address and queue before a client can connect to it. The broker can optionally be configured to automatically delete addresses and queues when queues and the broker will automatically create queues for each subscription when the consumers connect to address.foo . Then when a message is sent to address.foo it will be routed to each queue for there are scenarios where a user may want to statically configure a subscription queue and later connect to that queue directly using a Fully Qualified Queue Name (FQQN). Model 50 An FQQN uses a special

required. This saves you from having to preconfigure each address and queue before a client can connect to it. The broker can optionally be configured to automatically delete addresses and queues when queues and the broker will automatically create queues for each subscription when the consumers connect to address.foo . Then when a message is sent to address.foo it will be routed to each queue for there are scenarios where a user may want to statically configure a subscription queue and later connect to that queue directly using a Fully Qualified Queue Name (FQQN). Model 51 An FQQN uses a special

When clients connect to an address with the multicast element, a subscription queue for the client will be automatically automatically created for the client. It is also possible to pre-configure subscription queues and connect to them directly using the queue's Fully Qualified Queue names. Optionally add one or more queue elements are able to select the queue that they would like to subscribe to. Should more than one consumer connect directly to a single queue, Apache ActiveMQ Artemis will take care of distributing messages between

required. This saves you from having to preconfigure each address and queue before a client can connect to it. The broker can optionally be configured to automatically delete addresses and queues when queues and the broker will automatically create queues for each subscription when the consumers connect to address.foo . Then when a message is sent to address.foo it will be routed to each queue for there are scenarios where a user may want to statically configure a subscription queue and later connect to that queue directly using a Fully Qualified Queue Name (FQQN). Model 56 An FQQN uses a special

required. This saves you from having to preconfigure each address and queue before a client can connect to it. The broker can optionally be configured to automatically delete addresses and queues when queues and the broker will automatically create queues for each subscription when the consumers connect to address.foo . Then when a message is sent to address.foo it will be routed to each queue for there are scenarios where a user may want to statically configure a subscription queue and later connect to that queue directly using a Fully Qualified Queue Name (FQQN). Model 55 An FQQN uses a special

required. This saves you from having to preconfigure each address and queue before a client can connect to it. The broker can optionally be configured to automatically delete addresses and queues when queues and the broker will automatically create queues for each subscription when the consumers connect to address.foo . Then when a message is sent to address.foo it will be routed to each queue for there are scenarios where a user may want to statically configure a subscription queue and later connect to that queue directly using a Fully Qualified Queue Name (FQQN). Model 56 An FQQN uses a special

This saves you from having to preconfigure Model 46 each address and queue before a client can connect to it. The broker can optionally be configured to automatically delete addresses and queues when queues and the broker will automatically create queues for each subscription when the consumers connect to address.foo . Then when a message is sent to address.foo it will be routed to each queue for there are scenarios where a user may want to statically configure a subscription queue and later connect to that queue directly using a Fully Qualified Queue Name (FQQN). An FQQN uses a special syntax