Hello,
looking for some help around systemUsage and destinationPolicy configuration
as I'm having some difficulty fully understanding the relationship between
systemUsage, destinationPolicy, and flow control.
All our messages are persistent! producerFlowControl is on.
So we give ActiveMQ say a maximum of 512MB heap space.
Our systemUsage is set as below:
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage limit="200 mb"/>
</memoryUsage>
<storeUsage>
<storeUsage limit="10 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="1000 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
Our destination policy as below:
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" producerFlowControl="true" memoryLimit="1mb">
<pendingSubscriberPolicy>
</pendingSubscriberPolicy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
Please verify the if the following is correct:
This means that for each individual queue/topic the memory limit is 1MB.
What exactly happens when this 1MB is hit, does the queue block or does it
page to disc?
The total allowed memory for all queues and topics is 200MB. Meaning that
we could have 200 channels operating at their full capacity of 1MB. We
currently have 16 queues and topics in total so obviously that is never
reached.
Are we better to remove the individual policy entry on the memory limit and
share the memory between the various channels?
If we do this at what point would they block?
Any help very much appreciated! Can paypal you some beer money!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/systemUsage-and-destinationPolicy-config-tp3867059p3867059.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
