Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 558864

Summary: JMS_QPID_DESTTYPE is not set making getJMSDestination unusable.
Product: Red Hat Enterprise MRG Reporter: Arnaud Simon <asimon>
Component: qpid-javaAssignee: Rajith Attapattu <rattapat+nobody>
Status: CLOSED ERRATA QA Contact: Jiri Kolar <jkolar>
Severity: medium Docs Contact:
Priority: high    
Version: 1.2CC: gsim, jkolar
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the 'JMS_QPID_DESTTYPE' variable was not set making the 'getJMSDestination' method unusable.
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 16:10:09 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 Arnaud Simon 2010-01-26 15:36:51 UTC
See: JMS_QPID_DESTTYPE is not set making getJMSDestination unusable.
This breaks the JMS 1.1 compatibility

Comment 1 Gordon Sim 2010-01-26 15:47:21 UTC
See also https://issues.apache.org/jira/browse/QPID-2242

Comment 2 Rajith Attapattu 2010-03-09 15:20:39 UTC
I fixed it in rev 911251 in Qpid trunk.
Verified that existing tests pass. I would be adding a test with a custom exchange to test this code.

Leaving it open until the test it put in place.

Comment 3 Rajith Attapattu 2010-03-23 22:50:50 UTC
Added a test with a destination containing a custom exchange at rev 926829 in Qpid trunk.

Comment 5 Jiri Kolar 2010-09-22 11:36:44 UTC
which test do you mean? raise Needinfo

Comment 6 Rajith Attapattu 2010-10-01 13:50:27 UTC
This issue was tracked upstream via QPID-2242
The test that I am referring to above is testGetDestinationWithCustomExchange method in JMSDestinationTest.java.

Comment 7 Jiri Kolar 2010-10-04 12:54:38 UTC
fixed in qpid-java-client-0.7.946106-10.el5
mentioned test passes

validated on RHEL5.5/RHEL 4.8  i386 / x86_64

packages:
# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u
openais-0.80.6-16.el5_5.7
openais-devel-0.80.6-16.el5_5.7
python-qpid-0.7.946106-14.el5
qpid-cpp-client-0.7.946106-17.el5
qpid-cpp-client-devel-0.7.946106-17.el5
qpid-cpp-client-devel-docs-0.7.946106-17.el5
qpid-cpp-client-ssl-0.7.946106-17.el5
qpid-cpp-mrg-debuginfo-0.7.946106-14.el5
qpid-cpp-server-0.7.946106-17.el5
qpid-cpp-server-cluster-0.7.946106-17.el5
qpid-cpp-server-devel-0.7.946106-17.el5
qpid-cpp-server-ssl-0.7.946106-17.el5
qpid-cpp-server-store-0.7.946106-17.el5
qpid-cpp-server-xml-0.7.946106-17.el5
qpid-java-client-0.7.946106-10.el5
qpid-java-common-0.7.946106-10.el5
qpid-tools-0.7.946106-11.el5
rhm-docs-0.7.946106-5.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-53

->VERIFIED

Comment 8 Martin Prpič 2010-10-10 10:24:02 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the 'JMS_QPID_DESTTYPE' variable was not set making the 'getJMSDestination' method unusable.

Comment 10 errata-xmlrpc 2010-10-14 16:10:09 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html