Re: ActiveMQ Classic 6.1.1 Broker Name not updated in Web Console Network Bridge Tab after failover of Remote Broker

2024-09-30 Thread Matt Pavlovich
Hi Arthur- Yes, you would nest the two nodes for the peer primary and failover hosts. For the primary1 and failover1 nodes you would do: uri="masterslave:(tcp://primary2:61616, tcp://failover2:61616)..." Matt Pavlovich > On Sep 30, 2024, at 12:45 PM, Arthur Rodriguez wrote: > > HI Matt - > >

Re: ActiveMQ Classic 6.1.1 Broker Name not updated in Web Console Network Bridge Tab after failover of Remote Broker

2024-09-30 Thread Arthur Rodriguez
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 wrote: > We are running ActiveMQ Classic 6.1.1 in a Shared File Sys