Bug 962361 - [RFE]: The link must be named for the durable subscription queues
[RFE]: The link must be named for the durable subscription queues
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Development
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: messaging-bugs
MRG Quality Engineering
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-13 05:32 EDT by Petr Matousek
Modified: 2013-05-16 12:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Matousek 2013-05-13 05:32:27 EDT
Description of problem:

The following JMS client behavior change puts the supported clients out of sync: please see bug 962347.
Per discussion with Rajith, this change was made on purpose (to ensure users don't create durable temp queues) and the check is very useful.

I'm filling this bz to let the developers consider whether this change shall be also reflected by other supported clients. If the check is going to be implemented in the c++ client as well, the issue shall be also cloned for python client.

Version-Release number of selected component (if applicable):
qpid-cpp-*-0.22-2
qpid-java-*-0.22-2

How reproducible:
100%

Steps to Reproduce:
1. Use the following address string for receiver: 
   "amq.topic/some_subject;{ link: { durable: true } }"
2. Exception when using JMS client, no exception using c++ client (durable subscription queue created)
  
Actual results:
Different behavior of supported clients 

Expected results:
Supported clients behaves the same way

Additional info:

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