[rabbitmq-discuss] missing header frame

Michael Klishin michael.s.klishin at gmail.com
Fri Aug 19 05:39:18 BST 2011

2011/8/19 Dominic Metzger <dominic at rightscale.com>

> Is there a valid case when I wouldn't receive a header frame? Does it have
> something to do with the redelivery of the message? I am seeing this on
> RabbitMQ version (v1.7.2).
> Example:
> ["receive",
>  #<AMQP::Frame::Method:0x11d58b24
>   @channel=1,
>   @payload=
>    #<AMQP::Protocol::Basic::Deliver:0x11d58660
>     @consumer_tag="example.com-events--588378867313",
>     @debug=1,
>     @delivery_tag=7700,
>     @exchange="events",
>     @redelivered=true,
>     @routing_key="">>]
> ["receive",
>  #<AMQP::Frame::Body:0x11aa54f4
>   @channel=1,
>   @payload=
>    "{\"timestamp\":1313535484445309}">]
> thanks & best regards

I haven't read AMQP 0.8 spec (which is what amqp gem before 0.8.0.RCs
implements) in a while but I cannot think of a case when the header may be
missing. My only suggestion is to not rely on "logging" of various clients
because they use different frame class names, framing strategies and so on.
Use Wireshark, it will tell you what is really going up and down the wire.
And, maybe upgrade to RabbitMQ 2.5.1 that still supports AMQP 0.8 as well as
AMQP 0.9.1.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110819/d052f9d6/attachment.htm>

More information about the rabbitmq-discuss mailing list