qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Hardy <sha...@redhat.com>
Subject Re: Understanding python-qpid map size limitations
Date Wed, 13 Feb 2013 22:48:06 GMT
On Wed, Feb 13, 2013 at 05:38:46PM +0000, Gordon Sim wrote:
> On 02/13/2013 08:49 AM, Steven Hardy wrote:
> >Hi,
> >
> >I'm trying to understand some differences encoding map datatypes between
> >qpid and rabbitmq (openstack project which needs to support both)
> >
> >It seems that we hit a limit of 2^16 bytes when encoding a map on qpid,
> >because the map appears to be encoded as a string (write_map in codec010.py)
> >
> >Looking at the amqp 0-10 spec, it says "An encoded map may contain up to
> >(4294967295 - 4) octets worth of encoded entries.", so I'm trying to
> >understand the 65535 byte limitation I'm hitting, since we do not appear to
> >hit the same problem when configured to use rabbit.
> >
> >Can anyone please advise - is this a bug in python-qpid, or an expected
> >limitation of the qpid implementation?
> I think that is a bug in python-qpid. Do you have a simple
> reproducer you could attach to a JIRA?

Not right now, but I can reproduce the problem repeatably[1], so I'm sure I can
come up with some minimal python code which demonstrates the problem fairly
easily.  If you think it is a bug, I'll try to do so and raise a JIRA report.



[1] : https://bugs.launchpad.net/heat/+bug/1072917

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message