Hi, You can setup the storeUsage in activemq.xml. It will limit the data store.
Regarding the db-xxx.log, it’s the transactional log files, and they should be removed when a transaction is done. If you see a lot of db-xxx.log, it means that you have lot of pending persistent messages. A classic mistake is a DLQ never purge: ActiveMQ stores the transaction (rotated every 32MB by default) for the pending message. It means that retention is the date of the oldest pending message. Check your DLQ and eventually use the sharedDeadLetterStrategy to automatically purge the DLQ after a timeout. A possible improvement (depending of the use case) is to reduce the size of the journal in KahaDB. If you need help for the setup of that, please let me know. Regards JB > Le 2 mars 2020 à 12:04, COURTAULT Francois > <francois.courta...@thalesgroup.com> a écrit : > > Hello everyone, > > In case we have slow consumer and fast producer, for persistent messages, > those ones are stored in db-x.log files. > In order to avoid a file system full, is there a way to limit the number of > files or the number of messages or something else ? > > Best Regards. > > >
