Hi Domenico,
thanks for the explanation but if that is correct then the documentation at
https://activemq.apache.org/components/artemis/documentation/latest/network-isolation.html
is horribly wrong as it *explicitly* states this option is for both master
and slave:
>>>
Quorum voting is used by b
Tim,
I understand your point of view completely. I have a customer that runs Oracle.
When they have moderate traffic they experience a failover event between the
Master/Slave. And it appears to come from an inability to access the lock in
time causing the slave to take over. When they first cam
Hi Lewis,
the `quorum-vote-wait` parameter only affects nodes that are acting as
backup. It defines the time that the backup nodes will wait for quorum vote
responses and not time to wait before sending a quorum vote request. So
this parameter is not useful to allow Backup-1 to participate in the
To confirm, are you saying that you're trying to use one Oracle database
for message storage and a different Oracle database for locking?
If so, would you mind explaining why you're not just using a single
database for both purposes? I have no idea if the configuration I think
you're describing is