[rabbitmq-discuss] Patching rabbitmq to get more information about framing exceptions

[Michael Klishin]

2011/7/21 Matthias Radestock <matthias at rabbitmq.com>

> That means the server got a content header or body frame, which in case of
> client->server communication can only be as part of a publish. The most
> likely cause is the client sending more content body frames than it should,
> e.g. a trailing empty frame.
>
> It should be possible to spot that from the tracer / wireshark.
>
>
Yes, it is purely a publishing issue and the idea of extra frames has
crossed my mind. Wireshark doesn't prove it though.


>
>  Is it a good idea to make Rabbit log such issues with more detail (it
>> shouldn't affect hot code path performance anyway)?
>>
>
> We wouldn't want to log complete frame contents since that would introduce
> a major DoS attack vector. Having said that, the error that is logged (and
> indeed returned to the client) should include some more info than it
> currently does. I have filed a bug for that.
>

I still need to find a way to patch my local rabbit copy to get more
information. What's a good way to keep a few recent frames around? Is it
possible to implement as a plugin?

-- 
MK

http://github.com/michaelklishin
http://twitter.com/michaelklishin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110721/b7fd8170/attachment.htm>