<div dir="ltr">Hello Tim,<div><br></div><div>I'm using debian 6 and 7, and indeed I think heartbeats would be a good start to prevent this kind of behaviour, but helas SimpleAqmpClient doesn't support it. Can you think of any workaround ?�</div>
<div><br></div><div style>Thank you so much,</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/20 Tim Watson <span dir="ltr"><<a href="mailto:watson.timothy@gmail.com" target="_blank">watson.timothy@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF"><div>This sounds a lot like the physical network connection has been severed, but the client isn't noticing for a very long time. What os are you using? Have you considered turning on heartbeats in your clients, be expedite detection of connection failures?</div>
<div><br></div><div>Cheers,</div><div>Tim</div><div><div class="h5"><div><br>On 20 May 2013, at 16:26, Michael Journo <<a href="mailto:gobadiah@gmail.com" target="_blank">gobadiah@gmail.com</a>> wrote:<br><br></div>
<div></div><blockquote type="cite"><div><div dir="ltr">
<p>Hello,</p>
<p><br></p>
<p>I've came across a problem, but unfortunately I have very little information about it.</p>
<p><br></p>
<p>I use rabbitmq 2.8.4, along with clients such as pika (python side) and SimpleAmqpClient (c++ side). This issue was experienced in both those clients.</p>
<p><br></p>
<p>What happened is simply that DeclareQueue or queue_declare wouldn't return at all (I mean being blocked for <b>days</b>).�</p>
<p><br></p>
<p>When the incident started, I get a lot of�</p>
<p><br></p>
<p><br></p>
<p>=WARNING REPORT==== 18-May-2013::03:09:18 ===</p>
<p>closing AMQP connection <0.3256.1697> (<a href="http://127.0.0.1:46099" target="_blank">127.0.0.1:46099</a> -> <a href="http://127.0.0.1:5672" target="_blank">127.0.0.1:5672</a>):</p>
<p>connection_closed_abruptly</p>
<p><br></p>
<p>in the rabbitmq log, but nothing more.</p>
<p><br></p>
<p>I fixed this by � restarting rabbitmq, but I'm kind of worry because I don't know how to detect this problem again (building a timeout mechanism on top of the clients is just not ok).</p>
<p><br></p>
<p>If anyone has any idea about what could cause this, it would be greatly appreciated.</p><div><br></div>-- <br>michael
</div>
</div></blockquote></div></div><blockquote type="cite"><div><span>_______________________________________________</span><br><span>rabbitmq-discuss mailing list</span><br><span><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a></span><br>
<span><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a></span><br></div></blockquote></div><br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>michael
</div>