activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: How to configure 5.3 broker over KahaDB to support lots of unconsumed persistent msgs?
Date Tue, 26 Jan 2010 10:07:37 GMT
the memory limit puts a cap on the amount of memory a given destination can
consume. If 70% of that limit is reached, message enqueue blocks pending
release of some memory. If producerFlowControl is enabled, producers are
blocked pending some memory release.
The difference between the queue blocking and producerFlowControl is where
the block occurs. A blocked destination is waiting on the
broker, potentially blocking the connection. A blocked producer is blocked
on the client, allowing other consumers or producers to use the connection.

2010/1/26 Fred Moore <>

> Hi,
> going back to Cursors and
> ...
> ...can anyone shed some light on the actual role of memoryLimit in:
>    <policyEntry topic=">" producerFlowControl="false" memoryLimit="1mb">
>   <policyEntry queue=">" producerFlowControl="false" memoryLimit="1mb">
> ...moreover: *when* will producerFlowControl start slowing down consumers?
> Cheers,
> F.


Open Source Integration

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message