Anna,
Thanks for responding. After I disconnected all of the subscribers, and
then deleted the offline durable subscribers, the journal files were
purged, and the store usage went to 0.
It seems odd that had to be done in order to get the purge to run.
George
On 3/11/2023 6:43 AM, Anna
This is a case of "working as intended", if the software that uses durable
subscribers will not reconnect messages will be accumulating in internal
queue (this object is not visible as queue, but in webconsole in
"subscribers" tab).
And this messages plus journal files that cannot be dropped
I've made some headway on this, but could still use some help.
I went through and deleted all of the Offline Durable Topic Subscribers.
That freed up a little space (1%) in the store.
I notice there's a parameter /JournalFilesForFullRecovery that shows//a
value of 6500+. When I deleted the
I'm having problems now with an ActiveMQ instance running on AWS. I'm
running version 5.15.15 on an mq.m5.large instance, which is 4 cores and
16GB of memory.
There's a couple of DLQs that are empty, and one topic that sees maybe
50 messages a day. The AMQP connector shows 20 connections,
