Global memory limit for all queues / fileQueueCursor question

[Martin C.]

Hi,

I'm a little bit confused by all the memory limit options available in
ActiveMQ, maybe someone could help me. I primarily send non-persistent
messages, and I'd like them to be spooled to disk in case a global memory
limit is reached.

Basically, I'd like to set a global limit of 256MB for all queues together
(not per queue) and I'd like to spool the non-persistent messages and the
cursor to disk.

At the moment, I am using the following configuration, but according to
JConsole, it seems like the limits are not propagated correctly to the
queues (e.g. JConsoles shows a memory limit of 256 on every queue) and I see
heap-usage around 400-600MB at the moment.

    <systemUsage>
      <systemUsage sendFailIfNoSpace="true">
        <memoryUsage>
          <memoryUsage limit="256 mb" />
        </memoryUsage>
      </systemUsage>
    </systemUsage>

   <destinationPolicy>
      <policyMap>
        <policyEntries>
          <policyEntry topic=">" producerFlowControl="false">
          </policyEntry>
          <policyEntry queue=">" producerFlowControl="false">
            <deadLetterStrategy>
              <individualDeadLetterStrategy queuePrefix="DLQ."
useQueueForQueueMessages="true"
                processExpired="true" processNonPersistent="false" />
            </deadLetterStrategy>
            <pendingQueuePolicy>
              <fileQueueCursor />
            </pendingQueuePolicy>
          </policyEntry>
        </policyEntries>
      </policyMap>
    </destinationPolicy>

Thanks in advance for any pointer if this is correct or how I'd need to
adapt this in order to achieve what I described above.

Best regards,
Martin
-- 
View this message in context: 
http://old.nabble.com/Global-memory-limit-for-all-queues---fileQueueCursor-question-tp29449281p29449281.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.