I don't understand why send-to-dla-on-no-route won't work. You say, "...the underlying queues for federation within the multicast address are only created after the brokers have connected." Since the queues are not there then there will be no route so send-to-dla-on-no-route would seem to be the appropriate solution.
Justin On Mon, Apr 26, 2021 at 5:22 AM Dondorp, Erwin <[email protected]> wrote: > Hello, > > We are setting up brokers that use "federation" to move messages from the > first broker to the second. > In our case, it takes a while before the brokers have connected. This is > due to some slow network setup that we cannot control. > But the underlying queues for federation within the multicast address are > only created after the brokers have connected. > This causes some message loss as the clients happily produce messages on > an address with no underlying queues. > For any next startup, the queue will still be there. But many times, for > us, the startup is a "first" startup. > > Is there a way to prevent this message loss? > > We already tried to pre-define the "federation.xxx" queues with the exact > same names. But that leads to a broken system in which the federation > channel does not even work anymore. > There may be any number of local consumers on the first node, so any trick > using send-to-dla-on-no-route is not so useable. > > Thx! > Erwin >
