[rabbitmq-discuss] rabbitmq-c + 1.6.0 = bad headers
David Hawthorne
dhawth at 3crowd.com
Thu Apr 28 01:00:10 BST 2011
I saw this, which indicates that rabbitmq-c should Just Work:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2009-June/003858.html
Note that I'm using the rabbitmq-cpp wrapper around it (I think it's called amqpcpp officially).
client sees:
Expected 0x000A000A method frame on channel 0, got frame type 65
servers log shows:
=INFO REPORT==== 27-Apr-2011::23:55:28 ===
accepted TCP connection on 0.0.0.0:5672 from 127.0.0.1:51239
=INFO REPORT==== 27-Apr-2011::23:55:28 ===
starting TCP connection <0.19296.210> from 127.0.0.1:51239
=ERROR REPORT==== 27-Apr-2011::23:55:28 ===
exception on TCP connection <0.19296.210> from 127.0.0.1:51239
{bad_header,<<65,77,81,80,0,0,9,1>>}
=INFO REPORT==== 27-Apr-2011::23:55:28 ===
closing TCP connection <0.19296.210> from 127.0.0.1:51239
Any help you can give on this would be greatly appreciated. I'm testing against 1.6.0 because that's what apt-get gave me, but I'm not averse to upgrading.
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110427/f4700838/attachment.htm>
More information about the rabbitmq-discuss
mailing list