Bug 975451
| Summary: | can't create shared topic subscription queue over AMQP 1.0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Gordon Sim <gsim> |
| Component: | qpid-cpp | Assignee: | Gordon Sim <gsim> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matousek <pematous> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | Development | CC: | esammons, iboverma, jross, pematous |
| Target Milestone: | 3.0 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qpid-cpp-0.22-5.el6, qpid-cpp-0.22-5.el5 | Doc Type: | Bug Fix |
| 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: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 974061, 1010399 | ||
This issue has been fixed. Verified on rhel6.5 (x86_64, i386). packages under test: qpid-cpp-*-0.22-30 -> VERIFIED |
Description of problem: In 0-10 you could specify the details of the queue in the link and this allowed multiple receivers to share the same 'subscription' to the exchange. This was not available over AMQP 1.0 in qpid 0.22. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. qpid-receive --connection-options {protocol:amqp1.0,container-id:client1} --address 'amq.fanout; {assert:true, link:{name:my-sub}, node:{capabilities:[shared]}} -f 2. qpid-receive --connection-options {protocol:amqp1.0,container-id:client2} --address 'amq.fanout; {assert: true, link:{name:my-sub}, node:{capabilities:[shared]}} -f 3. check queues via qmf 4. send messages to amq.fanout Actual results: Assertion fails as shared capability is not recognised Expected results: step 3: only one should have been created, with two subscribers step 4: messages should be distributed between the two receivers rather than each getting all of them Additional info: