I have experienced an issue with the above: in the case that the
FailoverTransport attempts to connect to a broker configured for SSL using tcp:
scheme it loops forever seeking to (re-)establish a connection .
I am concerned at the impact this may have on our product, in that it is
consumed
Domenico,
That is a very helpful answer, thanks!
(as we can stop searching for the cause)
e.
-Oorspronkelijk bericht-
Van: Domenico Francesco Bruscino
Verzonden: vrijdag 28 mei 2021 16:52
Aan: users@activemq.apache.org
Onderwerp: Re: connectionLoadBalancingPolicyClassName for
Hi Erwin,
looking at the source code[1] the server side connector ignores all
addresses other than the first one. I would add a connector for each server.
[1]
Hello,
We want to use the federation in a "fair" way and added
connectionLoadBalancingPolicyClassName=org.apache.activemq.artemis.api.core.client.loadbalance.RandomConnectionLoadBalancingPolicy
to the connection url. But we see that the connections are still always made
to the first
Hi Steffen,
your application is getting the `AMQ229213` error[1] because artemis uses
not durable queue to implement the ActiveMQ Advisory Message[2].
To fix this error grant the `createNonDurableQueue` permission to the
`client1` user[3] or disable the advisory support adding the
Hi all,
Being inexperienced with messaging and ActiveMQ, I considered
replacing an ActiveMQ 5.16 broker installation with Artemis, and I
wonder if this is possible without having to upgrade the Java based
clients ?
On the Artemis broker, I have a simple acceptor:
