Bug 558864 – JMS_QPID_DESTTYPE is not set making getJMSDestination unusable.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 558864 - JMS_QPID_DESTTYPE is not set making getJMSDestination unusable.

Summary:	JMS_QPID_DESTTYPE is not set making getJMSDestination unusable.

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-java (Show other bugs)
Sub Component:
Version:	1.2
Hardware:	All Linux

Priority	high Severity medium
Target Milestone:	1.3
Target Release:	---
Assigned To:	Rajith Attapattu
QA Contact:	Jiri Kolar
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-01-26 10:36 EST by Arnaud Simon
Modified:	2010-10-14 12:10 EDT (History)
CC List:	2 users (show)

See Also:
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 12:10:09 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0773	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3	2010-10-14 11:56:44 EDT

Groups: None (edit)

Description Arnaud Simon 2010-01-26 10:36:51 EST

See: JMS_QPID_DESTTYPE is not set making getJMSDestination unusable.
This breaks the JMS 1.1 compatibility

Comment 1 Gordon Sim 2010-01-26 10:47:21 EST

See also https://issues.apache.org/jira/browse/QPID-2242

Comment 2 Rajith Attapattu 2010-03-09 10:20:39 EST

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 18:50:50 EDT

Added a test with a destination containing a custom exchange at rev 926829 in Qpid trunk.

Comment 5 Jiri Kolar 2010-09-22 07:36:44 EDT

which test do you mean? raise Needinfo

Comment 6 Rajith Attapattu 2010-10-01 09:50:27 EDT

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 08:54:38 EDT

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 06:24:02 EDT

    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 12:10:09 EDT

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

Note You need to log in before you can comment on or make changes to this bug.