Re: non-standard cluster topology

2021-02-18 Thread Justin Bertram
ugh exactly the same cluster-connections and > connectors are used. > And then the server is no longer part of the cluster as intended... > > Erwin > > -Oorspronkelijk bericht- > Van: Justin Bertram > Verzonden: donderdag 18 februari 2021 19:19 > Aan: users@ac

RE: non-standard cluster topology

2021-02-18 Thread Dondorp, Erwin
onnections and connectors are used. And then the server is no longer part of the cluster as intended... Erwin -Oorspronkelijk bericht- Van: Justin Bertram Verzonden: donderdag 18 februari 2021 19:19 Aan: users@activemq.apache.org Onderwerp: Re: non-standard cluster topology EXTERNAL SE

Re: non-standard cluster topology

2021-02-18 Thread Justin Bertram
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

non-standard cluster topology

2021-02-18 Thread Dondorp, Erwin
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