Hide Forgot
Description of problem: When ring queue overwrite detection mechanism (qpid.queue_msg_sequence) is used, Broker sets this value correctly but as String type instead of Integer type. Version-Release number of selected component (if applicable): qpid-cpp-0.22-19 How reproducible: 100% Steps to Reproduce: 1. create ring queue with qpid.queue_msg_sequence and send message ./spout.py "ringq;{create:always, 'node': {'x-declare': {'arguments': {'qpid.policy_type': 'ring', 'qpid.queue_msg_sequence': 'my_seq' }}}}" 2. receive a message ./drain.py "ringq" Actual results: Message(user_id='', correlation_id='', properties={'x-amqp-0-10.routing-key': u'ringq', u'my_seq': u'2', u'spout-id': '9ce80c9c-545e-4f23-bbe6-5ce2bdfced5b:0'}, content_type=u'') Expected results: Message(user_id='', correlation_id='', properties={'x-amqp-0-10.routing-key': u'ringq', u'my_seq': 2, u'spout-id': '9ce80c9c-545e-4f23-bbe6-5ce2bdfced5b:0'}, content_type=u'') Additional info: This is not a problem of drain.py client, type error was observed also by client with type detection, also other langs are affected.
Fixed upstream: https://svn.apache.org/r1532716
This issue was tested on Rhel 6.4 i686 and x86_64 with packages: perl-qpid-0.22-5.el6 perl-qpid-debuginfo-0.22-5.el6 python-qpid-0.22-5.el6 python-qpid-qmf-0.22-20.el6 qpid-cpp-client-0.22-23.el6 qpid-cpp-client-devel-0.22-23.el6 qpid-cpp-client-devel-docs-0.22-23.el6 qpid-cpp-client-rdma-0.22-23.el6 qpid-cpp-client-ssl-0.22-23.el6 qpid-cpp-debuginfo-0.22-23.el6 qpid-cpp-server-0.22-23.el6 qpid-cpp-server-devel-0.22-23.el6 qpid-cpp-server-ha-0.22-23.el6 qpid-cpp-server-rdma-0.22-23.el6 qpid-cpp-server-ssl-0.22-23.el6 qpid-cpp-server-store-0.22-23.el6 qpid-cpp-server-xml-0.22-23.el6 qpid-cpp-tar-0.22-16.el6 qpid-java-client-0.23-4.el6 qpid-java-common-0.23-4.el6 qpid-java-example-0.23-4.el6 qpid-proton-c-0.5-6.el6 qpid-qmf-0.22-20.el6 qpid-tools-0.22-6.el6 and behave as expected.
since this is skip_errata+ -> ON_QA -> VERIFIED