Hi, Also what was noticed in my test is that - when the CursorMemoryUsage reached/exceeded the limit (64MB), the producer was blocked (which is understandable) - but it was surprising to note that consumer was also blocked (i.e. the camel route that pulled messages from the Queue also froze) - is this an expected behavior?
Shouldn't the consumer consume messages even if producer was blocked? regards #D -- View this message in context: http://activemq.2283324.n4.nabble.com/Query-around-ActiveMQ-DLQ-tp4666277p4666406.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
