[rabbitmq-discuss] uninterruptibleGet() in basicCancel (Java Client)

Michael Klishin mklishin at gopivotal.com
Thu Mar 27 14:31:23 GMT 2014

On 27 March 2014 at 18:25:39, Gary Russell (grussell at gopivotal.com) wrote:
> > Is this a known (or fixed) issue...
> https://jira.spring.io/browse/AMQP-386 ?

Yes: https://bugzilla.rabbitmq.com/show_bug.cgi?id=25708

> It looks like the java client is blocked in basicCancel() waiting  
> for a reply.
> Based on the line numbers, it looks like he's using the default  
> (old) version of the client (2.8.4) pulled in by the old version  
> of Spring AMQP he's using (1.1.3).

The issue was that when you invoke a blocking operation (e.g. basic.consume or queue.declare)
from a basic.cancel handler, continuations deadlocked. 

Software Engineer, Pivotal/RabbitMQ

More information about the rabbitmq-discuss mailing list