<div dir="ltr"><div><div>Thanks for quick response Matthias.<br><br></div>And just to ease any concern, I misspoke earlier. Almost all of our clusters are on 3.0.2. However I personally run a newer version for testing and had forgotten that fact.<br>
<br></div>Matt<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 16, 2013 at 7:42 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Matt,<div class="im"><br>
<br>
On 17/07/13 00:26, Matt Pietrek wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We're seeing a bunch of failure messages from our Ruby clients to<br>
RabbitMQ 3.0.2. From the client side, we see 541 "Internal Error"<br>
<br>
On the server side logs, we see a bunch of errors. Normally I can at<br>
least hazard a guess what's wrong, but I have no idea with this:<br>
<br>
<br>
=ERROR REPORT==== 16-Jul-2013::22:43:15 ===<br>
** Generic server <0.4358.0> terminating<br>
** Last message in was {can_send,<0.4355.0>,true}<br>
** When Server state == {lim,1,<0.4359.0>,false,[],1}<br>
** Reason for termination ==<br>
** {function_clause,[{orddict,<u></u>update,<br>
<br>
[<0.4355.0>,#Fun<rabbit_<u></u>limiter.3.113433752>,[]],<br>
[{file,"orddict.erl"},{line,<u></u>153}]},<br>
{rabbit_limiter,limit_queue,2,<u></u>[]},<br>
{rabbit_limiter,handle_call,3,<u></u>[]},<br>
{gen_server2,handle_msg,2,[]},<br>
{proc_lib,init_p_do_apply,3,<br>
[{file,"proc_lib.erl"},{line,<u></u>227}]}]}<br>
<br>
</blockquote>
<br></div>
I think this is a duplicate of the problem reported at <a href="http://rabbitmq.1065348.n5.nabble.com/Rabbit-3-1-1-crash-question-td27540.html" target="_blank">http://rabbitmq.1065348.n5.<u></u>nabble.com/Rabbit-3-1-1-crash-<u></u>question-td27540.html</a>, the fix for which will appear in the next bugfix release.<br>
<br>
However, we were quite that the bug was only introduced in 3.1.0, so it's surprising to see this in 3.0.2. The code has certainly changed a lot on that area, so I'd advise upgrading in any case.<br>
<br>
Regards,<br>
<br>
Matthias.<br>
</blockquote></div><br></div>