Hi Arthur- I’m not aware of it being reported. Please create a JIRA ticket with the detail on how to reproduce and we can look at working on a fix in an upcoming release.
Thanks, Matt > On Sep 25, 2024, at 10:29 AM, Arthur Rodriguez <artrod...@gmail.com> wrote: > > Hi Matt - > > We have tried using masterslave, it has no impact on the issueI am > describing in this post. > Broker Name not updated in Web Console Network Bridge Tab after failover of > Remote BrokerPlease see my original post and let me know if you are aware > of the issue being reported and weather or not there is a known solution. > > Thanks, > Arthur Rodriguez > > On Thu, Sep 19, 2024 at 1:03 PM Matt Pavlovich <mattr...@gmail.com> 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 masterslave:// prefix seems more what you are looking for-- one >> network bridge to one of the brokers listed in the comma separated list of >> uni’s. >> >> >> https://activemq.apache.org/components/classic/documentation/networks-of-brokers#NetworksofBrokers-MasterSlaveDiscovery >> >> Thanks, >> Matt Pavlovich >> >>> On Sep 19, 2024, at 11:03 AM, 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? >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
