[rabbitmq-discuss] A non-AMQP exit

Matthias Radestock matthias at rabbitmq.com
Thu Oct 11 21:15:56 BST 2012


On 11/10/12 18:22, Michael Klishin wrote:
> While verifying a fix for amq-client today, I've noticed that a
> couple of amqp gem examples that previously passed no longer do. One
> of them is
> https://github.com/ruby-amqp/amqp/blob/6c3774efe71bd65e18a45fbd4511b3104a5d2dd7/spec/integration/multiple_consumers_per_queue_spec.rb#L263-319
>  Here's what the log (rabbitmq-server 2.8.7) reveals:
> https://gist.github.com/fa2f90216c4587a82cca
> Function in question is https://gist.github.com/61951978dab3b7e742df

The most likely reason is a client sending a basic.consume and following 
that up straight away with a basic.cancel w/o waiting for the 
basic.consume_ok first. Such pipelining of synchronous commands is not 
permitted by the spec.



More information about the rabbitmq-discuss mailing list