I then perform the following actions: Please find attached the spring boot publisher and subscriber demo application. Steps: 0. Start the broker cluster. 1. Start the producer application. 2. Let the producer published a few messages and then start the subscriber application. 3. Stop the subscriber application [amqp-demo-subscriber] . 4. Stop the first broker in the connection list causing the publisher application to failover to the second broker in the list. 5. Stop the publisher application (after some messages have been published to the second broker). 6. Start the subscriber application. (which connects to the second broker in the list, because the first one is still down). 7. Start the first broker in the connection list.   Now messages that were produced after the subscriber was stopped at step 3 are lost.   The cause of this issue seems to be that the queue in the multicast address that is automatically created in the first broker when starting the subscriber application isn't automatically replicated to the second broker. The second broker, therefore, isn't aware of the subscription when the publisher application starts publishing to this address (after the first broker has been stopped) and the published messages vanish. Is it possible to update the configuration of the broker cluster such that the auto-created multicast address with its (subscription) queues are automatically replicated to the other broker instances in the cluster?