On 22 Jul 2015 at 10:46:18, Nuttanart Pornprasitsakul (visiblet...@gmail.com)
wrote:
> 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.
Thanks, this is a fairly busy week for me with 3 releases but I will take a look
in the next few days.
> 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}]}]}
This means your version doesn’t have that function (it’s fairly new, I think
3.5.x)
--
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.
