>> Am I correct in believing that the broker doesn't sanity check the message size field against the received data?
I'm not sure there is a good way the broker can do that. The only way the broker knows if the message was corrupted is when it is unable to read the header of the next message. When this happens, it's unclear if the size or payload of the message was corrupted. The only message size check that a broker does is to check if a message is within max.message.size, which is configurable on the server. I guess if the message had a footer in addition to a header, we might be able to mitigate this to some extent, but that will require extra overhead per message. Thanks, Neha On Mon, Dec 10, 2012 at 3:43 AM, ben fleis <b...@monkey.org> wrote: > Am I correct in believing that the broker doesn't sanity check the message > size field against the received data?
