Okay, I think I have understood the difference. As we tend to have very small
transactions or immediate commits this will not make much of a difference in
our use case.
Last question:
The example you showed demonstrates how to starve the client,because of the
limit in max-read/prefetch. In a rea
> ...I had issues with configuration so decided to look into JMX exporter
as a workaround.
To be clear, the "JMX exporter" [1] is a tool provided by Prometheus to
read values from JMX MBeans and export them to a format which Prometheus
can consume (i.e. scrape via HTTP). It has nothing to do with
just to make my response a bit clearer: max-read will look into the pending
acks, while prefetch will only look at what's currently in the queue.
(that's a TL;DR (Too long, didn't read) of my previous messages).
On 2025/01/22 16:29:21 Clebert Suconic wrote:
> The logic is not complex.. the whol
The logic is not complex.. the whole thing is controlled here. The source code
will be a very good documentation in this case:
https://github.com/apache/activemq-artemis/blob/1ba0b65babf298e4dc47951aa6998b2d0ac02be6/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/QueueIm
sure...
I originally did not want to implement prefetch.. but my user had a case where
they needed a soft limit and a hard limit
At max-read, the system will stop fetching for data... period... no more
messages will come.
With Prefetch.. if you receive the messages on the consumer, it will
I am pleased to announce the release of ActiveMQ Artemis Console 1.1.0
*Downloads
https://activemq.apache.org/components/artemis-console/download/
*Complete list of updates
https://activemq.apache.org/components/artemis-console/download/release-notes-1.1.0
I would like to highlight these impro
