On 21 Jul 2015 at 11:17:50, Nuttanart Pornprasitsakul (visiblet...@gmail.com) wrote: > Follow up from the issue #74 I created on > Github(https://github.com/michaelklishin/langohr/issues/74). > Sorry that I posted there. > > It doesn't eventually unblock, both in and out queue are in idle > state not flow state. I'll get back again with the log and thread > dump.
There’s nothing unusual in the thread stack traces. We need a Wireshark protocol capture. rabbitmqctl eval `rabbitmq_diagnostics:maybe_stuck().` output may also help. -- MK Staff Software Engineer, Pivotal/RabbitMQ -- You received this message because you are subscribed to the Google Groups "clojure-rabbitmq" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure-rabbitmq+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
