[rabbitmq-discuss] rabbitmq-c corrupt content frame from ARM client

Simon MacMullen simon at rabbitmq.com
Mon Apr 7 18:49:52 BST 2014


On 07/04/2014 18:40, Alan Antonuk wrote:
>
> *To one of the RabbitMQ broker developers*: for the following message in
> the RabbitMQ broker logs:
>
>      =ERROR REPORT==== 3-Apr-2014::15:05:35 ===
>      closing AMQP connection <0.380.0> (192.168.1.117:52890
> <http://192.168.1.117:52890/>
>      <http://192.168.1.117:52890 <http://192.168.1.117:52890/>> ->
> 192.168.1.133:5672 <http://192.168.1.133:5672/>
>      <http://192.168.1.133:5672 <http://192.168.1.133:5672/>>):
>
>      {handshake_error,starting,0,
>                        {amqp_error,frame_error,
>                                    "type 0, first 16 octets =
>      <<5,10,0,11,0,0,0,80,98,112,____114,111,100,117,99,116>>...",
>
>                                    none}}
>
> Are those first 16 octets including or not including the frame header?

No, they don't. 5 is the first byte of the frame body. The frame was 
decoded as type 0, channel 0. The type 0 is of course rather dubious. 
Unfortunately that error message doesn't include the frame payload size, 
so some information for the frame header is missing.

Cheers, Simon


More information about the rabbitmq-discuss mailing list