Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 517836 - exclusive parameter ignored in JMS url binding, if durable attribute is present
exclusive parameter ignored in JMS url binding, if durable attribute is present
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java (Show other bugs)
1.1.6
All Linux
medium Severity medium
: 1.3
: ---
Assigned To: Rajith Attapattu
Jiri Kolar
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-17 08:43 EDT by Jiri Kolar
Modified: 2010-10-14 12:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, an exclusive parameter was ignored in JMS URL binding, if a durable attribute was present. This caused the created queue to not be marked exclusive, even though the property was specified in the binding URL. With this update, the exclusive parameter is set to TRUE when the queue declare is issued and the queue created is now exclusive.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-14 12:14:59 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)
jar with java test (82.72 KB, application/octet-stream)
2009-08-18 03:59 EDT, Jiri Kolar
no flags Details


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

  None (edit)
Description Jiri Kolar 2009-08-17 08:43:37 EDT
Description of problem:
If we use JMS url to create destination and we use "durable" parameter together with "exclusive", "exclusive" paramter is ignored. If durable is not present, exclusive works fine.

Version-Release number of selected component (if applicable):
qpid-dotnet-0.4.738274-2.el5
qpidc-rdma-0.5.752581-26.el5
qpidd-devel-0.5.752581-26.el5
qpidd-xml-0.5.752581-26.el5
qpid-java-client-0.5.751061-8.el5
qpidc-ssl-0.5.752581-26.el5
qpidd-ssl-0.5.752581-26.el5
qpidc-perftest-0.5.752581-26.el5
qpidc-debuginfo-0.5.752581-26.el5
python-qpid-0.5.752581-3.el5
qpidd-0.5.752581-26.el5
qpidd-rdma-0.5.752581-26.el5
qpidd-cluster-0.5.752581-26.el5
qpid-java-qman-0.5.751061-8.el5
qpidc-0.5.752581-26.el5
qpidd-acl-0.5.752581-26.el5
ruby-qpid-0.4.749380-2.el5
qpid-java-common-0.5.751061-8.el5
qpidc-devel-0.5.752581-26.el5

How reproducible:
always

Steps to Reproduce:
1. install qpid packages
2. install sun java
3. download attached jar file, go to directory with jar file

4. create queues with exclusive and durable parameters:

java -classpath `find "/usr/share/java/" -name '*.jar' | tr '\n' :`:QueueTest.jar com.redhat.mrg.test.client.queue.QueueTest --mode jms --queue-name test --thread-cnt 5 --queue-cnt 10  -e amq.direct --session-per-thread --queue-durable --queue-exclusive -r keyy

5. run:
qpid-config queues

that shows queues but only --durable option is present and excl is missing

6. delete created queues

7. create queues that are exclusive only:

java -classpath `find "/usr/share/java/" -name '*.jar' | tr '\n' :`:QueueTest.jar com.redhat.mrg.test.client.queue.QueueTest --mode jms --queue-name test --thread-cnt 5 --queue-cnt 10  -e amq.direct --session-per-thread --queue-exclusive -r keyy

8. run:
qpid-config queues

that shows queues with exclusive flag

Actual results:
If durable is present , exclusive parameter is ignored

Expected results:
both exclusive and durable should be applied

Additional info:
Comment 1 Jiri Kolar 2009-08-18 03:59:14 EDT
Created attachment 357747 [details]
jar with java test
Comment 2 Jiri Kolar 2009-08-26 11:07:40 EDT
just to be precise,, there have to be space between '\n' and : in command under 7. copy and paste may cause problems
Comment 4 Rajith Attapattu 2010-02-17 22:53:25 EST
This is fixed along with the new addressing syntax support.
It's available from rev 906145 and upwards in Qpid trunk.
Comment 5 Jiri Kolar 2010-09-07 07:22:03 EDT
this appeared since 1.1.6 and
is already fixed on qpid-java-client-0.5.751061-9.el5
retested on qpid-java-client-0.7.946106-8

validated on RHEL5.5/RHEL4  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-12.el5
qpid-cpp-client-0.7.946106-12.el5
qpid-cpp-client-devel-0.7.946106-12.el5
qpid-cpp-client-devel-docs-0.7.946106-12.el5
qpid-cpp-client-ssl-0.7.946106-12.el5
qpid-cpp-mrg-debuginfo-0.7.946106-11.el5
qpid-cpp-server-0.7.946106-12.el5
qpid-cpp-server-cluster-0.7.946106-12.el5
qpid-cpp-server-devel-0.7.946106-12.el5
qpid-cpp-server-ssl-0.7.946106-12.el5
qpid-cpp-server-store-0.7.946106-12.el5
qpid-cpp-server-xml-0.7.946106-12.el5
qpid-java-client-0.7.946106-8.el5
qpid-java-common-0.7.946106-8.el5
qpid-tools-0.7.946106-8.el5
rhm-docs-0.7.946106-4.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-53


->VERIFIED
Comment 6 Rajith Attapattu 2010-10-07 14:20:37 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:
Cause: exclusive parameter ignored in JMS url binding, if durable attribute is present.

Consequence: The queue created is not marked exclusive, even though the property is specified in the binding URL.

Fix: The exclusive parameter is set to true when the queue declare is issued.

Result: The queue created is now exclusive.
Comment 7 Martin Prpič 2010-10-10 07:31:42 EDT
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1 @@
-Cause: exclusive parameter ignored in JMS url binding, if durable attribute is present.
+Previously, an exclusive parameter was ignored in JMS URL binding, if a durable attribute was present. This caused the created queue to not be marked exclusive, even though the property was specified in the binding URL. With this update, the exclusive parameter is set to TRUE when the queue declare is issued and the queue created is now exclusive.-
-Consequence: The queue created is not marked exclusive, even though the property is specified in the binding URL.
-
-Fix: The exclusive parameter is set to true when the queue declare is issued.
-
-Result: The queue created is now exclusive.
Comment 9 errata-xmlrpc 2010-10-14 12:14:59 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.