I've tried the masterslave discovery agent on broker amq3 & the failover from
master (amq1) to slave (amq2) works.
However, masterslave doesn't seem to support priorityBackup=true & so the
broker doesn't fail-back from slave to master when the master comes back
online.
My original issue is that
I’ve come across a problem which has similar sounding symptoms & have done a
bit more investigation (no resolution yet though).
My problem is that when a network connector failed back to the remote broker
specified by the "priorityBackup" uri, the remote broker doesn't seem to
recognise that the c
I'm using a network of brokers & am trying to get a fail-back network
connection working (using priorityBackup=true on the connector)
I'm finding that the broker does failover & failback correctly but that the
remote broker doesn't seem to recognise that the re-established connection
is a network
