[rabbitmq-discuss] Channel crashes after basic.cancel_ok.

Ben Hood 0x6e6562 at gmail.com
Mon May 12 19:07:01 BST 2008


On 10 May 2008, at 01:02, Edwin Fine wrote:

> Thanks, Ben, I will take a look and give you some feedback.
> In the meantime, I have done the following:
> Changed my consumer code (I use the term "consumer" loosely as  
> "anything that eats the output of a producer") to use basic.get  
> instead of basic.consume. Actually, it's set up so that I can select  
> basic.get or basic.consume behavior at run-time. I didn't want to  
> throw away working basic.consume code :)
> Changed the process that creates consumers so that it now creates  
> one channel per consumer. Previously, there was one channel only for  
> all consumers. One-channel-per-consumer was the only way I could get  
> the code to work with the network client; in the one-channel  
> scenario I was getting back responses to messages destined for  
> different consumers. I assume that with your changes I will be able  
> to again use one channel for all consumers.
> I tested with 50 queues (each with its own consumer and channel) and  
> it seemed reasonably performant, even with the get. I need to try a  
> full-blast test soon.

I have now commited fix 2 of 3 to the mtn repo which addresses the  
issue of not being able to subscribe concurrently. So the 2 issues you  
mention here should be addressed.

The outstanding issue is to close the writer down properly in the  
network case.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080512/0bf60111/attachment.htm 

More information about the rabbitmq-discuss mailing list