<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" memoryLimit="10 mb"/>
<policyEntry topic=">" memoryLimit="10 mb">
<dispatchPolicy>
<strictOrderDispatchPolicy/>
</dispatchPolicy>
<subscriptionRecoveryPolicy>
<lastImageSubscriptionRecoveryPolicy/>
</subscriptionRecoveryPolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
Does that help ?
On Thu, Feb 5, 2009 at 4:45 AM, Dejan Bosanac <de...@nighttale.net> wrote:
> Hi Adam,
>
> can you post a configuration you were trying (with memoryUsage) and a client
> that can reproduce the problem. I saw your earlier post that you're using
> 5.1.0, did you try it with 5.2.0?
>
> Regards
> --
> Dejan Bosanac
>
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
> On Mon, Feb 2, 2009 at 7:09 PM, AD <straightfl...@gmail.com> wrote:
>
>> Hello,
>>
>> I get a lot of OutOfMem errors when the producers submit a very high
>> number of messages. I tried tweaking memoryUsage to a lower number to
>> force spooling to disk but it does not appear to help. It could also
>> be the consumers are requesting items too quickly (not sure yet).
>>
>> Is there a proper way to throttle the memory usage when a huge spike
>> of messages come in? Trying to accomodate for these instances since
>> whenever this happens activemq just dies.
>>
>> Thanks
>> Adam
>>
>
