I posted the code snippet that can cause the issue on github. Also posted
differences in network trace between blocking and success run that I've
noticed there.
The output from rabbitmqctl eval `rabbitmq_diagnostics:maybe_stuck().` is
Error: {undef,[{rabbitmq_diagnostics,maybe_stuck,[],[]},
{erl_eval,do_apply,6,[{file,"erl_eval.erl"},{line,657}]},
{rpc,'-handle_call_call/6-fun-0-',5,
[{file,"rpc.erl"},{line,205}]}]}
On Tuesday, July 21, 2015 at 5:47:44 PM UTC+7, Michael Klishin wrote:
>
> On 21 Jul 2015 at 11:17:50, Nuttanart Pornprasitsakul (visib...@gmail.com
> <javascript:>) 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.
