When enforcing either max-disk-usage or min-disk-free the broker looks at
the *whole* disk so that any data written to disk is considered in the
calculation. This, of course, applies to files in the broker's journal. It
also applies to data written by other processes. For example, if there was
anot
Hi Justin,
thanks for your reply.
There is just a latest point I would need to clarify.
Do the "max-disk-usage"/"min-disk-free" settings apply also to the persisted
messages, and not only to the paging behavior, right?
I will try to explain my test scenario a little more:
*
we are working with
Hello.
I'm going to create a JIRA.
I'm also going to find some other points, if any, to check the actual
state, with other Jolokia requests.
Thanks for your help.
Regards.
Le lun. 4 mars 2024 à 07:18, Jean-Baptiste Onofré a écrit :
>
> Hi
>
> Jolokia health service only considers the BrokerSe
Hello JB,
sorry to bother
I've seen in another thread you're familiar with Jolokia integration inside
ActiveMQ
Maybe you have got an advice also for me, on this thread?
Thank you so much in advance
*Distinti Saluti / *Kind Regards
M.G.
Il giorno ven 23 feb 2024 alle ore 14:24 Marco Garavello
Hello JB !
Hope you are well !
>1. The message goes in redelivery (because it expired or client
>rollback transaction) and so it can be taken by another consumer. As
>you use session_transacted, the "first" client has to deal with the
>rollback
For me that was not so likely because the message ar
Hi Matt !
Thanks for your answer. I understand email support for this kind of issue
is a bit hard.
We will double check on all this, check all logs.
I also understand that logging the messageId would be a great help to
identify what is happening, so we might consider that.
Best,
Fred
Le ven. 1
