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 -
>
>
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
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 create a J
I approved a request for Jira access for "Arthur Rodriguez" more than two
days ago. Maybe check your spam folder?
Justin
On Wed, Sep 25, 2024 at 12:06 PM Arthur Rodriguez
wrote:
> Hi Matt - I requested JIRA access on Monday of this week, so still awaiting
> approval, once I have access to subm
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 wrote:
>
> Hi Matt -
>
> We have tried using masterslave, i
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
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:03 PM Matt
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.
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
