Hi,
- We are setting up a cluster of 6 brokers using Artemis 2.4.0.
- The cluster has 3 groups.
- Each group has one master, and one slave broker pair.
- The HA uses replication.
- Each master broker configuration has the flag 'check-for-live-server' set to
true.
- Each slave broker
>>Are you sure about that -Xss1024m? That would set the thread stack size to
a
monstrous 1GB. Perhaps you wanted to configure the initial heap size (-Xms)
there but made a typo?
Thanks for the help. The framework that launches the Java application was
incorrectly setting default stack size to
Hi,
messages dequeued is the number of messages that has been consumed since
the broker start (it's cumulative, on all destinations).
Regards
JB
On 12/07/2018 16:20, libing195205 wrote:
> It's sad that nobody interests in it, could anyone help?
>
>
>
> --
> Sent from:
