HI Matt - Does MasterSlave discovery support nesting at all is is it not needed. For example can it be nested inside the static: tag or used along with the failover: transport ?
On Thu, Sep 19, 2024 at 12:03 PM Arthur Rodriguez <artrod...@gmail.com> wrote: > We are running ActiveMQ Classic 6.1.1 in a Shared File System Master Slave > HA environment with multiple brokers networked in a hub spoke architecture. > Broker Failover is working as expected, however in the web console on the > network bridge tab, the Broker Name does not get updated after failover of > any remote broker, the ip address does get updated and messages are > properly transmitted to the current “Master” as expected. > > I understand that the Broker Name is obtained from metadata when the > original connection is made and may not be immediately updated in the > console when the network bridge reconnects to the new Master broker after > failover however it seems to me that there should be some way to refresh > the broker name. > > Here is the network bridge config we are using: <networkConnector > conduitSubscriptions="false" duplex="true" name="MY-BRIDGE" networkTTL="2" > uri="static:(failover:(tcp://201.me.net:61002,tcp://202.me.net:61002))?nested.wireFormat.maxFrameSize=104857600&randomize=false&maxReconnectAttempts=-1"> > <staticallyIncludedDestinations> <queue physicalName="Q.A" /> <queue > physicalName="Q.B" /> <queue physicalName="Q.C" /> <queue > physicalName="Q.D" /> </staticallyIncludedDestinations> </networkConnector> > > > > Can anyone provide some insight on how we might be able to refresh the > Broker Name field without needing to restart the network adapter, which > might require a restart of the broker in the worst case scenario? >
