[rabbitmq-discuss] Non-blocking Consumers approach

Mahesh Viraktamath yuva670 at gmail.com
Mon Aug 27 08:58:54 BST 2012


We used RabbitMQ to implement a simple producer-consumer architecture.
It was fine until very recently, when we encountered the blocking
calls. I ran two nodes in a cluster; in cases where the consumer took
more than the usual time and all subsequent messages kept on waiting.
Then, I came to know that I used QueuingConsumer which is a blocking
architecture, now I know I have to use my own implementation of the
DefaultConsumer. But, I am clueless as to whether I should manage the
threading model or the RabbitMQ itself has any provision on that.
Another thing that is confusing is, whether we run different type of
consumers (with different duties) separately or we maintain a single
main class which will start consumers as the messages come in.

Thanks in advance,

More information about the rabbitmq-discuss mailing list