<div dir="ltr">Thank you, Michael. �The Tracer is a very cool tool. �Thanks for pointing it out! �It definitely confirms the issue regarding multiple opens:<div><br></div><div><div>1363291338032: <Tracer-0> ch#8 -> {#method<channel.open>(out-of-band=), null, ""}</div>
<div>1363291338032: <Tracer-0> ch#8 -> {#method<channel.open>(out-of-band=), null, ""}</div><div>1363291338070: <Tracer-0> ch#8 -> {#method<channel.open>(out-of-band=), null, ""}</div>
<div>1363291338070: <Tracer-0> ch#8 -> {#method<channel.open>(out-of-band=), null, ""}</div></div><div><br></div><div style>Now I still just have to figure out how/why they are being sent!</div><div style>
<br></div><div style>-Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 14, 2013 at 10:08 AM, Michael Klishin <span dir="ltr"><<a href="mailto:michael.s.klishin@gmail.com" target="_blank">michael.s.klishin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><div class="im">2013/3/14 Chris <span dir="ltr"><<a href="mailto:stuff@moesel.net" target="_blank">stuff@moesel.net</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>First, the non-node-specific question: �Does anyone have any pointers on how to debug such an issue? �I've already looked at logs and found which channel is the problem-- but if I comment out the code that creates that channel, then it just fails on a different channel the next time (btw-- you don't explicitly create channels in node-amqp, they are created for you when you subscribe to queues, declare exchanges, etc.).</div>
</blockquote><div><br></div></div><div>Using Wireshark or RabbitMQ tracer [1].</div><div class="im"><div>�</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div><br></div><div>And the more node-specific question: �RabbitMQ docs seem to indicate it is usually an error in the client (node-amqp in our case), but I wonder if perhaps we are making some newbie node-amqp mistake that might lead to this 503 error? �Is there anyone with node-amqp experience that has been through this before?</div>
</blockquote></div></div><br>This issue indicates a race condition when a library assumes it need to automatically open a channel after channel.open</div><div class="gmail_extra">has been sent. Or it may be because channel ids are not incremented properly in the client so two channels end up</div>
<div class="gmail_extra">having the same id.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Finally, race conditions can originate in your own code but it's impossible to tell without</div><div class="gmail_extra">
seeing the code.<br><br clear="all"><div>1. See at the bottom of�<a href="http://www.rabbitmq.com/api-guide.html" target="_blank">http://www.rabbitmq.com/api-guide.html</a></div><span class="HOEnZb"><font color="#888888">-- <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>
</font></span></div></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></div>