The only scenario I can think here on the loss of address/queues , noting that somehow your slave is thinking it can active as master (aka acceptors start up) is that auto-delete-queues/auto-delete-address is kicking in (which default is true I believe) as it deletes queue on no subscription and then address will delete on no queues. Which would occur if the slave is activating somehow as you’d have no subscriptions.
Seems that getting to bottom of why the slave is activating is prob the main priority here. Sent from my iPhone > On 21 Sep 2017, at 20:36, Michael André Pearce <michael.andre.pea...@me.com> > wrote: > > I’ve just tested manually (in a HA setup) that if you set delete policy to > OFF which by default it is set to OFF, then queues and address do not get > undeployed on reload. Eg queues and addresses if created in GUI or CLI > remain. > > Only if you change/override that to FORCE would it remove an address or queue > not defined in broker.xml. I assume here you have not set deletion policy to > FORCE, and just on default OFF > > It would be good/great help if you are able to make any form or reproducer > integration test if you still see this issue. > > > Cheers > Mike > > > > Sent from my iPhone > >> On 21 Sep 2017, at 20:16, Justin Bertram <jbert...@redhat.com> wrote: >> >> Many of the changes made via the management API are volatile. However, >> adding queues should be persistent. If reloading broker.xml causes queues >> added via the management API to disappear I think that's likely a bug.
