Thanks for the link, Tim - that article appears to exactly cover the problem
we were seeing. I applied policies like
to the queues which receive lots of large messages. The combination of
settings for the policy seems to prevent overrunning the heap cache, and
prevents starvation of consumers on
Hi Tim,
Yes - the consumers on Queue A will eventually start receiving messages once
Queue B has had a bunch of messages removed.
FWIW, I just verified this behavior is still present in 5.13.2.
Thanks,
-Aaron
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumers-in
I'm looking for some pointers in diagnosing an issue we're seeing. I'll try
to describe:
ActiveMQ version: 5.12.1
OS: Ubuntu Linux 12.04
STOMP clients using Ruby 2.0.0 stomp gem v 1.1.10
We have two queues on a host with 8GiB of RAM and 20GiB of disk space. Under
steady-state conditions...
Queue
