Right, so as far as I am aware the STRICT load balancing policy does not allow
for message redistribution, it's purpose is to divide incoming messages evenly
across the cluster regardless of client/consumer state. Perhaps ON_DEMAND might
be better suited for your needs, or possibly OFF_WITH_REDI
Hello,
In your cluster configuration, what "message-load-balancing"-type have you
configured?
Br,
Anton
This email message (including its attachments) is confidential and may contain
privileged information and is intended solely for the use of the individual
and/or entity to whom it is addres
82
M: +1 7209385761 |
john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com>
From: Roskvist Anton mailto:anton.roskv...@volvo.com>>
Sent: Thursday, November 10, 2022 12:32 PM
To: users@activemq.apache.org<mailto:users@activemq.apache.org>
Subject: RE: Practical l
Hello John,
For reference, one of the environments I'm maintaining currently uses around
3.5k active destinations. The broker cluster is running on relatively modest
servers without any issues. I will say though that at this point there has been
some noticeable slowdowns in precisely the areas
Hello Thomas,
I might be mistaken but I believe this has been fixed in broker version
2.20.0... it might be a good idea to update the broker version regardless since
there has been quite a few bug fixes, added features and improvements made
since 2.19.0. Be sure to follow the "Versions" documen
Hello John,
I believe the parameter you are looking for is: "initialConnectAttempts=-1" in
addition to what you have already configured. The default value is 0, meaning
try once and throw an exception if that does not work (which is what you are
seeing in your post).
Br,
Anton
From: John Lill
Hi,
I have been running with ZGC for quite some time and find it to be the superior
choice for my purposes.
With low to moderate load on the broker G1GC will be slightly faster in terms
of overall messages in+out of the broker.
However, system response times and latency is far better and more co
broker perspective, if this is intermittent behaviour from the OS that
we don't expect then we issue a warn, but there is little point flooding the
logs. Doing it once or once a day may be sufficient.
On Fri, 30 Apr 2021 at 10:39, Roskvist Anton wrote:
>
> Hi,
>
> I have a pro
Hi,
I have a problem with Artemis that I'd like some insight on... starting with
artemis-2.16.0 I was getting these WARN messages, followed by a broker shutdown:
WARN [org.apache.activemq.artemis.core.server] AMQ222010: Critical IO Error,
shutting down the server.
file=AIOSequentialFile:/path/t
