Until recently (1.5.0) you would only have the TTL to decide when to
activate backup.
Recently connection failures will also play in the decision to activate it.
So on 1.3.0 you will be bound to the TTL of the cluster connection.
On 1.5.2 ir should work with kill but you would still be bound
Hi all,
I finally figured out what was happening. Here are my conclusions, for future
reference.
In a nutshell:
* Every time a message expires on the consumer, the prefetch extension kicks in
and allows even more messages to be dispatched. Because the session is not
closed, the extended prefe
Forgot to send the attachments!
From: Gerrit Tamboer
Date: Thursday 26 January 2017 at 13:23
To: "users@activemq.apache.org"
Subject: Problems setting up replicated ha-policy.
Hi community,
We are attempting to setup a 3 node Artemis (1.3.0) cluster with an
active-passive failover situation.
Hi community,
We are attempting to setup a 3 node Artemis (1.3.0) cluster with an
active-passive failover situation. We see that the master node is actively
accepting connections:
09:52:30,167 INFO [org.apache.activemq.artemis.core.server] AMQ221000: live
Message Broker is starting with confi
