Hi,<br><br>I am investigating a rare (but nonetheless top priority) amqp gem issue when frames are delivered out of order. Neither the Tracer tool nor Wireshark give me<br>good understanding of what frame exactly RabbitMQ chokes on, it just says "expected a method frame, got a non-method frame instead".<br>
<br>So I am trying to patch RabbitMQ to get some more information. What's the right way to do it? Right now I am trying to make<br>rabbit_command_assembler:process/2 do what I want and I am not sure how to get a string representation of<br>
<br>1. Method that was delivered out of order.<br>2. # of the channel on which it happened<br>3. Ideally, 10-20 most recent frames<br><br>Can I ask someone from the RabbitMQ team help me a little bit? Where should I be looking? Is it a good idea to make Rabbit log such<br>
issues with more detail (it shouldn't affect hot code path performance anyway)?<br><br>At this point I have an app that reproduces the issue roughly every other time and I am using a Rabbit instance compiled from HEAD sources.<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>