I can't speak to Petter's scenario, but in my use case that's the intent: we don't want to allow an infinite number of messages to build up on the broker. But the slow consumer abort strategy is also a part of the protection strategy for the broker (since we primarily use topics with non-durable subscriptions and aborting a slow consumer will dump the messages it has built up) and we're unwilling to sacrifice the ability to abort slow topic consumers in order to get the more-granular memory protection. We'd love to have both, but to make that work they both have to be using the same metric for their counts (and it would be easier to switch memoryLimit to use message counts than to switch slow consumer abort strategy to use total bytes).
On Thu, Jan 8, 2015 at 3:28 PM, artnaseef <a...@artnaseef.com> wrote: > That's an interesting requirement. The memory usage limit is there to help > ensure the broker's resources are not exhausted. > > Is the end intent the same in using a message count? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-to-limit-queue-depth-by-msgs-tp4689633p4689670.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
