2011/7/21 Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Given that you can reproduce the problem easily, you may just want to log some details of all the frames - frame type, class id, method id, and for content headers the expected body size, and for content bodies the payload size.</blockquote>
</div><br>So far I narrowed it down to the "empty messages" problem: whenever there is an empty message sent by amqp gem master version, RabbitMQ<br>doesn't consider it a complete message and thus clients do not get anything. With a simple script that terminates as soon as the message is received<br>
(by the same process), this looks like app is hanging. In the context of a larger application, sometimes there are empty messages transmitted (I am streaming a stdout output).<br><br>After comparing 2 clients I see the following picture: the data transmitted is exactly the same, frame order is correct but Wireshark GUI suggests that<br>
one client transmits 3 frames as 3 IP packets. In this case, RabbitMQ is happy. The other transmits them all in a single IP packet and RabbitMQ doesn't seem to recognize it as a complete message.<br><br>Here are two Wireshark session exports:<br>
<a href="https://gist.github.com/1096404">https://gist.github.com/1096404</a><br><br>If the [frames] content is the same, what may be going on here?<br clear="all"><br>-- <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>