RE: ActiveMQ 5.16.x Master/Slave topology question

2021-12-01 Thread Vilius Šumskas
@activemq.apache.org Subject: Re: ActiveMQ 5.16.x Master/Slave topology question On Tue, 2021-11-30 at 17:20:31 +0100, Vilius Šumskas wrote: >[...] > As an alternative, does anybody know if I can use non-HTTP SSL load balancer > and set client URI to something like ssl://loadbalancer_host:61

Re: ActiveMQ 5.16.x Master/Slave topology question

2021-12-01 Thread Tim Bain
- Simon > > > -Original Message- > > From: Jean-Baptiste Onofré > > Sent: Tuesday, November 30, 2021 6:01 PM > > To: users@activemq.apache.org > > Subject: Re: ActiveMQ 5.16.x Master/Slave topology question > > > > Hi, > > > > masterslave:

Re: ActiveMQ 5.16.x Master/Slave topology question

2021-12-01 Thread Simon Lundström
t; Sent: Tuesday, November 30, 2021 6:01 PM > To: users@activemq.apache.org > Subject: Re: ActiveMQ 5.16.x Master/Slave topology question > > Hi, > > masterslave: transport is deprecated. You can achieve the same with > randomize=false basically. > > Correct: updateClusterClientOnRe

RE: ActiveMQ 5.16.x Master/Slave topology question

2021-11-30 Thread Vilius Šumskas
:)). -- Vilius -Original Message- From: Jean-Baptiste Onofré Sent: Tuesday, November 30, 2021 6:01 PM To: users@activemq.apache.org Subject: Re: ActiveMQ 5.16.x Master/Slave topology question Hi, masterslave: transport is deprecated. You can achieve the same with randomize=false

Re: ActiveMQ 5.16.x Master/Slave topology question

2021-11-30 Thread Jean-Baptiste Onofré
Hi, masterslave: transport is deprecated. You can achieve the same with randomize=false basically. Correct: updateClusterClientOnRemove is only for network connection, but when you have active/active (so a real network). No, the clients won't be stuck: they will reconnect to the new

RE: ActiveMQ 5.16.x Master/Slave topology question

2021-11-30 Thread Vilius Šumskas
, November 30, 2021 7:01 AM To: users@activemq.apache.org Subject: Re: ActiveMQ 5.16.x Master/Slave topology question Hi No need to use networkConnector with master/slave. Just use failover on the client side. So basically, 1. Brokers side, you shared the same filesystem (using NFS, LUN, whatever

Re: ActiveMQ 5.16.x Master/Slave topology question

2021-11-29 Thread Jean-Baptiste Onofre
Hi No need to use networkConnector with master/slave. Just use failover on the client side. So basically, 1. Brokers side, you shared the same filesystem (using NFS, LUN, whatever), and you configure kahadb to point on the same filesystem in activemq.xml 2. On client side, you can

ActiveMQ 5.16.x Master/Slave topology question

2021-11-29 Thread Vilius Šumskas
Hi, I‘m trying to setup a simple ActiveMQ 5.16.x master/slave cluster using shared filesystem option. I just need one broker running at any given time and a slave for HA. The filesystem part is clear and I have already configured it according to ActiveMQ requirements. What I don’t understand