Issue

• In our production environment in "/opt/jboss-amq-6.1/etc/activemq.xml" we set the "storeUsage" limit to 100GB.

<systemUsage>
    <systemUsage>
        <!-- default -Xmx for AMQ is 1G, so this will be 700M -->
        <memoryUsage>
            <!-- taken from activemq's default configuration -->
            <memoryUsage percentOfJvmHeap="70"/>
        </memoryUsage>
        <storeUsage>
            <storeUsage limit="100 gb"/>
        </storeUsage>
        <tempUsage>
            <tempUsage limit="50 gb"/>
        </tempUsage>
    </systemUsage>
</systemUsage>

• However because there was not a full 100GB on the disk when AMQ was installed only 27GB was allocated by AMQ for storeUsage limit. This has proven not to be enough space for all the messages we want to store in KahaDB and a system outage occurred when the limit hit 100%. We now have more disk space but we want to confirm that all we need to do is restart AMQ for this extra space to be allocated to storeUsage limit?

• We have found the below link which states "When the ActiveMQ broker is started, it checks to see if the disk space of the file system assigned to the message store (in this case it is the kahaDB) can accommodate the storeUsage limit." https://access.redhat.com/solutions/1436033.

• Does this mean a restart is all that is required now that we have the extra disk space?

• Persistent store is Full