blob: ec0389a8f37853956df0c3287c876157c4265bda [file] [log] [blame]
<div class="wiki-content maincontent"><p>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 version&#160;<strong style="line-height: 1.4285715;">5.12.0</strong>, it's possible to configure the Broker to periodically check disk space and reconfigure the limits accordingly using the broker attribute schedulePeriodForDiskUsageCheck &gt; 0.</p><p>For example a configuration like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ &lt;broker xmlns=&quot;http://activemq.apache.org/schema/core&quot; schedulePeriodForDiskUsageCheck=&quot;60000&quot;&gt;
...
&lt;/broker&gt;
]]></script>
</div></div><p>will check the store and temporary disk limits every 60 seconds (<code>schedulePeriodForDiskUsageCheck</code>&#160;option, default value is 0 which disables this check).</p><p>&#160;</p></div>