Hi, Just checked in the code, and you are right: storeUsage == db data (not journal log files).
Regards JB > Le 3 mars 2020 à 14:51, Tim Bain <tb...@alumni.duke.edu> a écrit : > > Based on https://dzone.com/articles/temp-store-and-memory-percent, it > sounds like storeLimit considers only the messages (db*.data) but not the > redo log. So the amount of disk used in total could be a bit larger than > the limit that's set. > > Tim > > On Mon, Mar 2, 2020, 6:48 AM Jean-Baptiste Onofre <j...@nanthrax.net> wrote: > >> Hi, >> >> storeUsage == db.data + db.log + redo AFAIR. >> >> Regards >> JB >> >>> Le 2 mars 2020 à 14:45, COURTAULT Francois < >> francois.courta...@thalesgroup.com> a écrit : >>> >>> Hello, >>> >>> What about this question below ? >>> >>>> Does it mean that if we set this value it will not create new >>>> db-xxx.log files if the number of db-xxx.log files * 32 Mb >= >> storeUsage value ? >>> >>> Best Regards. >>> >>> -----Original Message----- >>> From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com] >>> Sent: lundi 2 mars 2020 14:14 >>> To: users@activemq.apache.org >>> Subject: Re: Is it possible to limit the storage in ActiveMQ ? >>> >>> I don't know if you can specify the store size via the URL - I suspect >> not. >>> You can provide an activemq.xml config file for ActiveMQ running in >> TomEE - high level instructions are here: >>> >> https://tomee.apache.org/latest/docs/jms-resources-and-mdb-container.html >> - see the "Internal ActiveMQ Broker with activemq.xml" section. >>> >>> I second JB's comment though - people worry about the kahadb logs not >> getting removed and filling up the disk. Ensuring that all your messages >> are consumed or purged will ensure these files are cleaned up, rather than >> the store continually growing. >>> >>> One other note, running ActiveMQ embedded in TomEE will mean that >> resources are shared between the two. If you have large message volumes, it >> may be worth swapping to an standalone ActiveMQ broker, and pointing TomEE >> to that. Instructions for that are in the link above as well. >>> >>> Jon >>> >>> >>> >>> On Mon, Mar 2, 2020 at 1:01 PM COURTAULT Francois < >> francois.courta...@thalesgroup.com> wrote: >>> >>>> Hello Jean-Baptiste, >>>> >>>> Just for you to know : we are using ActiveMQ in TomEE context. >>>> >>>> You said: " You can setup the storeUsage in activemq.xml. It will >>>> limit the data store." >>>> Does it mean that if we set this value it will not create new >>>> db-xxx.log files if the number of db-xxx.log files * 32 Mb >= >> storeUsage value ? >>>> BTW, do you know how to set this storeUsage value in TomEE context ? >>>> could it be passed in this connection string >>>> broker:(tcp://localhost:61616)?usekahadb=true&kahadb.directory=.... >> ? >>>> >>>> Best Regards. >>>> >>>> -----Original Message----- >>>> From: Jean-Baptiste Onofre [mailto:j...@nanthrax.net] >>>> Sent: lundi 2 mars 2020 12:30 >>>> To: users@activemq.apache.org >>>> Subject: Re: Is it possible to limit the storage in ActiveMQ ? >>>> >>>> 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. >>>>> >>>>> >>>>> >>>> >>>> >> >>
