On Fri, Feb 15, 2013 at 04:48:05PM +0000, Gordon Sim wrote: > On 02/15/2013 04:39 PM, Steven Hardy wrote: > >I still find it interesting that we don't hit this problem on rabbitmq, but > >I guess that may have to be a mystery that can be solved another day ;) > > How is the message encoded in that case? Does it use an AMQP 0-9-1 > field-table? That version defines two types of strings - short > strings and long strings, the latter can be up to 2^32.
Sorry, I'm not really sure - all I know is all our users running qpid hit this bug[1] and all our users running rabbit do not. I've not personally done much testing on rabbitmq, but as you point out it seems to provide support for a different amqp version so that may well explain the difference we are seeing. Our code just publishes the message, so I don't have any real visibility of what happens under-the-hood on rabbit, although obviously I've dug into qpid a bit trying to understand this issue. FYI here's our code which interfaces to qpid/rabbit (common to all openstack projects): https://github.com/openstack/heat/blob/master/heat/openstack/common/rpc/impl_qpid.py https://github.com/openstack/heat/blob/master/heat/openstack/common/rpc/impl_kombu.py [1] : https://bugs.launchpad.net/heat/+bug/1072917 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
