Franz worked with the software mills guys. There is a blog post about it I
think with some recommendations.
I will see if I can find some links in the morning to add here.
On Thu, Oct 20, 2022 at 2:04 AM Clebert Suconic
wrote:
> The confirmation window size is definitely a change that needs to
The confirmation window size is definitely a change that needs to be done.
Is your benchmark a single producer / consumer ?
There is a lot of things we do to allow scale of multiple clients.
On Wed, Oct 19, 2022 at 4:08 PM Dave Fisher wrote:
> There is a project at the Linux Foundation called
There is a project at the Linux Foundation called https://openmessaging.cloud -
they include Artemis drivers in their Benchmark program - for both Artemis
here: https://github.com/openmessaging/benchmark/tree/master/driver-artemis and
Artemis JMS here:
https://github.com/openmessaging/benchmark
Basically I'm telling you how to investigate it.. and if you find an
issue on the broker, we will need a way to reproduce it.
I have no other report about a message loss situation...
(we do have situations with page-counters going wrong while
paging..which I'm working now to fix it... but no mes
I am not aware of any issues that would lead to message loss...
Garbage Collection itself has no effect on anything regarding paging or journal.
Are you able to chase which message is lost on a test?
you could use the retention feature, replay the message.. and you
could also look on the ./art
All,
This week we lost 23.000 messages in a few days time on our production
Cluster running Artemis 2.26.0, see our settings below. We've reverted
back to Artemis 2.20.0 just in case
A few observatoins:
* In version 2.24.0, 2.25.0 and 2.26.0 running on ZGC we noticed
messages being produ
