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 Jaworska wrote:
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 because they
are still in use is what causing the storage to get full.
Remeber that size of stored messages does not equal size of storage on the
disk, if there is a message assosciated with journal file, whole file will
remain on disk for a while, until journal reorganization kicks in, but this
itself is imperfect.
You can set timetolive for disconnected durable subscribers in activemq.xml
Check
https://activemq.apache.org/manage-durable-subscribers
It can also help to change size of journal files to smaller (default is
32Mb).
And for sanity make sure that messages delivered to broker have expiry set
and if not enforce it (there is a plugin for this )
pt., 10 mar 2023, 23:08 użytkownik George Sexton
--
George Sexton
(303) 438 9585 x102
MH Software, Inc.
