<br><br><div class="gmail_quote">2012/11/4 Daniel Neugebauer <span dir="ltr"><<a href="mailto:mailinglists@energiequant.de" target="_blank">mailinglists@energiequant.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":3b4">The other library would loose connection a few seconds after<br>
connecting but doesn't notice.</div></blockquote></div><br>With AMQP 0.9.1 structure (multiple channels share a connection, error handling mostly happens<div>on the per-channel basis), error handling and recovery is not trivial. amqp gem has automatic recovery</div>
<div>mode and in practice, it works surprisingly well but every once in a while someone disagrees about</div><div>what exactly it does by default.</div><div><br></div><div><a href="http://rubyamqp.info/articles/error_handling/">http://rubyamqp.info/articles/error_handling/</a><br clear="all">
<div><br></div><div>It certainly would be nice to have similar capabilities in other clients but I can see why it is</div><div>not obvious what actions client libraries should take by default.</div><div><br></div><div>Connection loss after a few seconds or error messages from clients sound unusual. Please</div>
<div>provide at least some information about your setup: whether the clients and RabbitMQ are on</div><div>the same machine or distributed, what the error messages are and what's in the RabbitMQ log.</div>-- <br>MK<br>
<br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br><br>
</div>