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

Bug 634043

Summary:	JMS client release notes for MRG 1.3 release.
Product:	Red Hat Enterprise MRG	Reporter:	Rajith Attapattu <rattapat+nobody>
Component:	Release_Notes	Assignee:	Lana Brindley <lbrindle>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	Development	CC:	mhideo
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	* Cause: When upgrading an existing application to use the new Qpid libraries, and the application does not use destinations defined using the Binding URL format * Consequence: The Qpid libraries will be not parsed properly as they will be interpreted based on the addressing format. * Fix: Workaround: Do one of the following: (a) Use -Dqpid.dest_syntax=BURL to switch the default destination syntax to Binding URL format. (b) Prefix each destination definition with "BURL:" Ex BURL:direct://amq.direct/MyQueue?routingkey='test' * Result: This ensures that destinations defined using the Binding URL are parsed properly without any error.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-14 20:43:27 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:
Bug Depends On:
Bug Blocks:	548214

Description Rajith Attapattu 2010-09-15 02:33:00 UTC

Description of problem:

The following items needs to be added to release notes.

(1) If your application is using Binding URL's to define destinations
---------------------------------------------------------------------
By default the destination strings used in the jndi.properties file or session.createQueue or session.createTopic are interpreted based on the Addressing format (and not as Binding URL's).

If you are upgrading an existing application (with destinations defined using
the Binding URL format), to use the new Qpid libraries, one of the following
needs to be done in order to ensure the destination definitions are parsed
correctly.

(a) Use -Dqpid.dest_syntax=BURL to switch the default destination syntax to
Binding URL format.

(b) Prefix each destination definition with "BURL:"
Ex BURL:direct://amq.direct/MyQueue?routingkey='test'

(20 If your application is using Durable Subscriptions created based on a destination defined using an addressing string
----------------------------------------------
Currently there is a bug that prevents successful failover if a Durable Subscriber is created using a destination defined using an addressing string.
Please see Bug 633942 for more details regarding the issue.

In order workaround this issue, please use a Binding URL to create the destination. Please also make sure to prefix it using "BURL" as the default is the Addressing format.

Ex. session.createTopic("BURL:my_durable_topic");

Comment 1 Rajith Attapattu 2010-09-15 02:48:53 UTC

Using the CCFR format to describe the above to items.

Issue #1
--------------
* Cause:        Upgrading an existing application to use the new Qpid libraries.

* Consequence:  If your application is using destinations defined using
the Binding URL format, they will be not parsed properly as they will be interpreted based on the addressing format.

* Fix:          One of the following needs to be done.
                (a) Use -Dqpid.dest_syntax=BURL to switch the default destination syntax to Binding URL format.

                (b) Prefix each destination definition with "BURL:"
                    Ex BURL:direct://amq.direct/MyQueue?routingkey='test'


* Result:       This ensures that destinations defined using the Binding URL are parsed properly without any error.


Issue #2
--------------
* Cause:        Using a Durable Subscription created based on a Destination defined using an addressing string.

* Consequence:  It prevents your application from failing over properly in the event of a broker failure. Please see Bug 633942 for more details regarding the issue.

* Fix:          Please use a Binding URL to create the destination. Please also make sure to prefix it using "BURL" as the default is the Addressing format.

Ex. session.createTopic("BURL:my_durable_topic");


* Result:       This ensures that your application performs failover as expected.

Comment 2 Lana Brindley 2010-09-17 00:13:57 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:
* Cause: When upgrading an existing application to use the new Qpid libraries, and the application does not use destinations defined using the Binding URL format
* Consequence: The Qpid libraries will be not parsed properly as they will be interpreted based on the addressing format.
* Fix: Workaround: Do one of the following:
(a) Use -Dqpid.dest_syntax=BURL to switch the default
destination syntax to Binding URL format.
(b) Prefix each destination definition with "BURL:"                     Ex BURL:direct://amq.direct/MyQueue?routingkey='test'
* Result: This ensures that destinations defined using the Binding URL are parsed properly without any error.

Comment 3 Lana Brindley 2010-09-23 03:59:22 UTC

Revision 0.1 of the release notes will available for review on the stage shortly.

LKB

Comment 4 Lana Brindley 2010-10-14 20:43:27 UTC

Release Notes have now  been published:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/html/MRG_Release_Notes/index.html

LKB