Hi,
storeUsage == db.data + db.log + redo AFAIR.
Regards
JB
> Le 2 mars 2020 à 14:45, COURTAULT Francois
> 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 *
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
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
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
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
Hello,
I suppose you're talking about Artemis but I am using ActiveMQ and not Artemis.
I should highlight this in my first post.
Any solution for ActiveMQ ?
Best Regards.
-Original Message-
From: brusdev [mailto:bruscin...@gmail.com]
Sent: lundi 2 mars 2020 12:20
To:
Hi,
the System will perform scans on the disk to determine if the disk is beyond
a configured limit. These are configured through `max-disk-usage` in
percentage. Once that limit is reached any message will be blocked. (unless
the protocol doesn't support flow control on which case there will be
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.
