Bug 556764

Summary: Add support for AMQP 0-10 based map message to JMS client
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-javaAssignee: Rajith Attapattu <rattapat+nobody>
Status: CLOSED ERRATA QA Contact: Jeff Needle <jneedle>
Severity: medium Docs Contact:
Priority: urgent    
Version: DevelopmentCC: rmusil
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-20 11:30:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gordon Sim 2010-01-19 10:53:26 UTC
Description of problem:

The python and c++ clients support a map message based on the AMQP 0-10 map encoding. The JMS client's map message format is non-standard and less rich. It would therefore be beneficial to add support for an AMQP 0-10 map encoded message to the JMS client.

Comment 1 Rajith Attapattu 2010-02-18 03:34:47 UTC
This is tracked via QPID-2363 in upstream.
rev 903940 and up in Qpid trunk should contain the required support.

Comment 2 Jiri Kolar 2010-03-16 10:41:07 UTC
Could you please provide reporducer or at least info how to verify it? Thanks

Comment 3 Rajith Attapattu 2010-03-17 17:03:13 UTC
Write a Java client that sends/receives map messages.
(look at AMQPEncodedMapMessageTest.java for examples)

Run that against the C++ and python map message examples.
For python & c++ you can use spout/drain examples.

Comment 4 Jiri Kolar 2010-04-08 17:30:37 UTC
Tested:
on qpid-java-client-0.5.751061-9.el5 message is send but is incomplete.
on qpid-java-client-0.7.916826-2 message is ok.

# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u

openais-0.80.6-16.el5
openais-debuginfo-0.80.6-16.el5
python-qpid-0.7.917557-4.el5
qpid-cpp-client-0.7.916826-2.el5
qpid-cpp-client-devel-0.7.916826-2.el5
qpid-cpp-client-rdma-0.7.916826-2.el5
qpid-cpp-client-ssl-0.7.916826-2.el5
qpid-cpp-mrg-debuginfo-0.7.916826-2.el5
qpid-cpp-server-0.7.916826-2.el5
qpid-cpp-server-cluster-0.7.916826-2.el5
qpid-cpp-server-devel-0.7.916826-2.el5
qpid-cpp-server-rdma-0.7.916826-2.el5
qpid-cpp-server-ssl-0.7.916826-2.el5
qpid-cpp-server-store-0.7.916826-2.el5
qpid-cpp-server-xml-0.7.916826-2.el5
qpid-dotnet-0.4.738274-2.el5
qpid-java-client-0.7.918215-1.el5
qpid-java-common-0.7.918215-1.el5
qpid-tools-0.7.917557-4.el5


->VERIFIED

Comment 5 Jiri Kolar 2010-04-14 08:19:35 UTC
validated on RHEL  5.5 i386 / x86_64  and
 RHEL 4.8 i386 / x86_64