How many messages do you have in the broker when this happens? There is a sync period which may take a short while, particularly if there's a lot of data in the broker or the connection between the live and backup is slow.
Essentially what is happening during this period is. 1. Master starts up checks to see if there is broker running with the same ID. 2. Same ID found, master starts as slave 3. Master starts replicating the live node until both nodes are in sync. 4. Live is then shutdown 5. Master takes over as live 6. Slave starts as backup. Sync happens again for the backup (in case any messages were sent during it's shutdown). You will experience some delay during this sync period, the length depends on how many messages you have in the broker. That said, I have seen issues where the master hangs on failback. So, I'll take a look here. Could you also let me know if you have many persisted messages and could you try again and just wait a little longer to ensure it's not the expected delay described above. Thanks On Tue, Jun 21, 2016 at 3:23 PM, Sebastian Dellwig < sebastian.dellwig....@iqser.com> wrote: > Hi Martyn, > I tried it now with version 1.3.0. > Same behavior. > I waited a couple of minutes, but the failback does not happen. > Instead both permanently post: AMQ212034: There are more than one servers > on > the network broadcasting the same node id. > > I'll send you my broker.xml files. > > Thanks in advance. > > -Sebastian > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Artemis-Automatic-failback-does-not-work-tp4713190p4713197.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
