It's being done as part of this PR:
https://github.com/apache/activemq-artemis/pull/4246
On Fri, Oct 14, 2022 at 4:40 AM Robbie Gemmell wrote:
>
> That helper command doesnt exist yet as Clebert said since the idea
> only came from discussing something else the other day, but the
> pre-existing
thank you-- will advise
On Wed, Oct 12, 2022 at 11:03 PM Tetreault, Lucas
wrote:
> Hey James,
>
> For what it's worth... You can continue using static:(failover:(uri1,
> uri2)) with the addition of the following query params
> "?randomize=false&maxReconnectAttempts=0" which is functionally equiv
Am Freitag, dem 14.10.2022 um 09:22 +0100 schrieb Robbie Gemmell:
> A very similar report came in a couple months ago, and the reason was
> that the session (/children) was incorrectly being used from multiple
> threads, causing responses operations to 'overlap' and leading to a
> ClassCastExceptio
Hi,
We're considering using Message Groups to solve update contention within
the consumers.
Consumers do handle contention by rolling back and retrying, which
significantly reduces effective throughput, so the objective is to
eliminate as much contention as possible.
Msg ordering is also not str
That helper command doesnt exist yet as Clebert said since the idea
only came from discussing something else the other day, but the
pre-existing logging related changes coming for 2.27.0 are covered in
the docs along with diffs of the script changes from 2.26.0, you can
see the current source versi
A very similar report came in a couple months ago, and the reason was
that the session (/children) was incorrectly being used from multiple
threads, causing responses operations to 'overlap' and leading to a
ClassCastException when the mismatching responses for a different
operation arrived.
On Th
