That's certainly not the expected behavior. A handful of clustering
examples ship with the broker with valid configurations you can compare
against. If that doesn't help feel free to provide your broker configs here
with steps to reproduce.
Justin
On Thu, Feb 18, 2021 at 2:42 PM Dondorp, Erwin
Justin,
That is what I expected too. And it is one of the scenarios that I tried.
Indeed, the status turns green while stating "HA Policy: Live Only".
But at the same time, that server is no longer connecting to the other cluster
members, even though exactly the same cluster-connections and
I believe the "red cross" is showing up because you've defined an ha-policy
in your broker.xml and designated the broker explicitly as a master. It
therefore expects a backup to be available, and since there is no backup it
displays the red cross.
If you just take the ha-policy out of broker.xml
Hello,
In the cluster topology, one can define a server as "master" or "slave".
For a specific application, only non-persistent messages are present.
(and non-persistent messages are not sent to the slave servers)
This makes the master/slave situation a bit useless; and so, I want to use only
Samuel-
If you are getting a response from port 61616, there is a good chance you have
it going. However, your best bet is to check with the Debian Package
maintainer. It sounds like the installation moved some files to different
locations than the default from the Apache ActiveMQ
Hi there,
For JS client over protocol STOMP, sometimes we are getting connection errors,
where client apparently is not able to reconnect anymore, even if restarting
the client:
errno":"ECONNRESET","code":"ECONNRESET"
And broker side, we found:
Could not start TLS encryption. TLS error
Dear all,
I’m completely new to ActiveMQ and only have very little prior experience with
message queues, so please bear with me.
I just installed ActiveMQ 5.15.8 on Debian 10, using the package from the
official repositories:
https://packages.debian.org/buster/activemq
If I understand
Hello,
Using Artemis, I have messages that are entering the broker as non-persistent
messages.
But, I need to make the messages persistent as soon as possible. So preferably
within the broker.
Is there any predefined method to do that? (I could not find one...)
Or is this a job for a custom
