What info can you provide about how clients are consuming from the queues?
Any chance there are a bunch of messages "inflight" which haven't been
ack'd by the consumer?


On Wed, Jan 2, 2013 at 10:20 AM, Mohit Anchlia <mohitanch...@gmail.com>wrote:

> I see these messages being logged. Queues are setup to use persistent
> store. I am wondering what's causing this messages to get blocked. I see
> there is a memoryLimit but if I am using persistent=true then should this
> be the desired behaviour?
>
>
> 2013-01-02 05:06:13,388 | INFO |
> Usage(default:memory:queue://eventsEndpoint:memory) percentUsage=0%,
> usage=0, limit=20971520,
> percentUsageMinDelta=1%;Parent:Usage(default:memory) percentUsage=106%,
> usage=22366029, limit=20971520, percentUsageMinDelta=1%: Usage Manager
> Memory Limit reached. Producer
> (ID:pfdamq301.ie.net-54582-1351809386355-2:1:1:1) stopped to prevent
> flooding queue://eventsEndpoint. See
>
>
>    <broker xmlns="http://activemq.apache.org/schema/core";
> brokerName="static-broker1" persistent="true"
> dataDirectory="${activemq.data}">
>
>         <!-- Destination specific policies using destination names or
> wildcards -->
>         <destinationPolicy>
>             <policyMap>
>                 <policyEntries>
>                     <policyEntry queue=">" producerFlowControl="true"
> memoryLimit="20mb">
>                         <deadLetterStrategy>
>                           <individualDeadLetterStrategy queuePrefix="DLQ."
> useQueueForQueueMessages="true" />
>                         </deadLetterStrategy>
>                     </policyEntry>
>                     <policyEntry topic=">" producerFlowControl="true"
> memoryLimit="20mb">
>                     </policyEntry>
>                 </policyEntries>
>             </policyMap>
>         </destinationPolicy>
>
>         <!-- Use the following to configure how ActiveMQ is exposed in JMX
> -->
>         <managementContext>
>             <managementContext createConnector="true"/>
>         </managementContext>
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Reply via email to