This issue has been identified while validating if the Dispatch Router is reconnecting properly with the Broker in an HA scenario, when Master instance fails over to the Slave and then fails back to the Master.

When the Master is restarted (and the backup server stops its acceptor), the Dispatch Router attempts to reconnect with the master broker as soon as it detects that its acceptor's port is available, and we noticed that the open frame received by the Router (from AMQ), sometimes, does not have the "fail-over-list" present in the properties. So, if the master now goes down, Interconnect will keep trying to connect to the master repeatedly since it has deleted the slave broker's connection information.

Instead, Interconnect must not forget the previous failover urls. If a situation like the above happens, Interconnect could connect back to the slave if the master goes down.