We're developing a strategy for backups and HA. Ideally we'd like to use
colocated backups to ensure data integrity and availability with scale-down
configured from the slave to the master host.
We ran into an issue when bringing a server back up, consider this
situation.
Servers 1 and 2 are brou
> No way to confirm cluster members are connecting as expected
When cluster members connect to each other there should be a message logged
about the bridge that is formed between them. Aside from that, you can use
the listNetworkTopoloy management operation (I think that's exposed by EAP,
but not
I don't believe the 5.x broker has duplicate detection functionality.
Justin
On Fri, Jan 18, 2019 at 3:00 PM funnysage wrote:
> Hi Justin,
>
> Thanks for the reply. Yes I understand that detection is at broker level
> and
> that is how it should be.
> Now what I have learnt is that we are not
Hi Justin,
Thanks for the reply. Yes I understand that detection is at broker level and
that is how it should be.
Now what I have learnt is that we are not using Artemis but ActiveMQ 5.18.
So will this feature be there in 5.18 too? Or I have to some other approach.
Thanks
--
Sent from: http://
If you put a message into a queue (i.e. instead of the database) then the
broker will make sure that only one consumer get it (assuming you're using
anycast routing). This replaces the DB locking mechanism you want to avoid.
The duplicate-detection functionality that you referenced is for the
*bro
Hi all,
Does ActiveMQ fully supports OpenJDK 11 ? I have done couple of tests with
OpenJDK11, it is working fine . But does it fully supports OpenJDK 11 or is
there a future plan for the same ?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
