[rabbitmq-discuss] .NET client hangs on BasicGet

Peter Townsend Peter.Townsend at mflow.com
Wed Jan 13 17:55:34 GMT 2010

Hi all,

I'm using the .NET client running against a windows installation of the RabbitMQ broker. I have found that calls to IModel.BasicGet(...) will hang after process a number of message. The number of messages processed before it hangs changes with each run.

I refactored to use a BasicConsume approach and I find a similar issue, the consumer stops receiving messages after a number have been processed and there are still remaining message in the queue. Has anyone had a similar experience with the .NET client API?

I'm out of ideas :) The consumer class (including channel setup) I'm using is attached (using direct exchange to a named, durable, queue).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100113/99d1a52e/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: MessageConsumer.cs
Url: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100113/99d1a52e/attachment.txt 

More information about the rabbitmq-discuss mailing list