Thanks for the link, Tim - that article appears to exactly cover the problem we were seeing. I applied policies like
<policyEntry queue="QueueB" useCache="false" cursorMemoryHighWaterMark="10" /> 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 other queues. -Aaron -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumers-inexplicably-blocked-while-producers-run-fine-Help-tp4710793p4710862.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
