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

Thu Mar 27 14:37:29 GMT 2014

Thanks, Michael.

On Thu, Mar 27, 2014 at 10:31 AM, Michael Klishin <mklishin at gopivotal.com>wrote:

> 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.
> --
> MK
>
> Software Engineer, Pivotal/RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140327/58eae0a3/attachment.html>