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
It is entirely against the JMS spec requirements, and thus similarly
non-portable, yes.
On Thu, 19 Sept 2024 at 11:57, wrote:
> Hello Robbie.
>
> I have found a solution to set the client ID and use shared topics in
> different clients at the same time.
> The option
>
> connectionFactor
Hello Robbie.
I have found a solution to set the client ID and use shared topics in
different clients at the same time.
The option
connectionFactory.setEnableSharedClientID(true);
does the trick. May it be against JMS spec or not, everything works fine.
Regards
Herbert
Von:
