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

2024-09-25 Thread Arthur Rodriguez
Hi Matt - I requested JIRA access on Monday of this week, so still awaiting approval, once I have access to submit tickets I will do just that. Thanks, Arthur Rodriguez On Wed, Sep 25, 2024 at 1:01 PM Matt Pavlovich wrote: > Hi Arthur- > > I’m not aware of it being reported. Please

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

2024-09-25 Thread Arthur Rodriguez
not there is a known solution. Thanks, Arthur Rodriguez On Thu, Sep 19, 2024 at 1:03 PM Matt Pavlovich wrote: > Hi Arthur- > > Would you please try this without using failover? Network Connectors > reconnect by default, so you should not use the failover uri://. > > The mastersla

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

2024-09-19 Thread Arthur Rodriguez
Hi Matt - Thanks for the quick response, the team tells me that they tried using masterslave:// with a lot of exceptions, it is likely to be early next week before we can test it again. I'll update this thread once we are able to test. Thanks, Arthur Rodriguez On Thu, Sep 19, 2024 at 1:

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

2024-09-19 Thread Arthur Rodriguez
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