Periodically checking disk limits

Features > Persistence > Periodically checking disk limits

Store and temporary disk limits are set for the Broker on startup based on configuration and available space. Sometimes other processes (such as logs) can grow and reduce the available disk space enough that the limits detected at start up no longer have any effect. Since ActiveMQ Classic version 5.12.0, it’s possible to configure the Broker to periodically check disk space and reconfigure the limits accordingly using the broker attribute schedulePeriodForDiskUsageCheck > 0.

For example a configuration like

<broker xmlns="" schedulePeriodForDiskUsageCheck="60000">

will check the store and temporary disk limits every 60 seconds (schedulePeriodForDiskUsageCheck option, default value is 0 which disables this check).

Apache, ActiveMQ, Apache ActiveMQ, the Apache feather logo, and the Apache ActiveMQ project logo are trademarks of The Apache Software Foundation. Copyright © 2024, The Apache Software Foundation. Licensed under Apache License 2.0.