OK, please see this jira ticket and vote for it!
https://issues.apache.org/jira/browse/AMQ-5522
Please make comments in the ticket, or let me know, if any updates to the
ticket are desired.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-limit-queue-depth-by
e 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-tp4
>689633p4689670.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ge 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.
>
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-dep
Tim,
Thanks for the reply. Prefetch is not really a problem, since in this
scenario I tend to use 1 as reliability is the only concern, not
performance in this case.
Number of messages is sometime a better measurement than memory, and a
more valid constraint. It¹s easier to cope with a requirement
Petter,
I'm not aware of a way to limit queue depth by number of messages that will
invoke producer flow control, which is the behavior I assume you want to
result when you hit the limit. We actually just disabled per-destination
memory limits in our broker because of the difficulty of guaranteei
Hi,
Is there a way to limit the queue depth of an ActiveMQ queue in number of
messages?
I know there are ”per destination policies” that can detect queue usage in
terms of memory used. However, the number of messages may indicate other
things, like how many .log files (kahadb) that can be tied
