title: RabbitMQ frame_too_large exception
body: <p>I published a message into a queue and consumer is expected to fail to parse the message and put it into DLQ, but the message gets stuck at Unacked state.
  The exception I can see is </p>
  
  <blockquote>
    <p>ERROR : #method(reply-code=501,
    reply-text=FRAME_ERROR - type 2, all octets = &lt;&lt;>>:
    {frame_too_large,206219,131064}, class-id=0, method-id=0)</p>
  </blockquote>
  
  <p>The message is is actually less than default frame size but bumps up to this big when it tries to drop it to DLQ.
  RabbitMQ is configured to default frame_max=131072. If its increased to greater than 206219 works fine and successfully goes to DLQ.
  Not sure if it is calculating size of message including exception thrown and other metadata that ends of with frame_too_large error.</p>
  
  <p>Is it better idea to increase the frame_max ? or what might be the better approach ?</p>