Bug 1069757
| Summary: | Can't disambiguate name for which both queue and exchange exist | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Gordon Sim <gsim> | |
| Component: | python-qpid | Assignee: | Gordon Sim <gsim> | |
| Status: | CLOSED ERRATA | QA Contact: | Irina Boverman <iboverma> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.0 | CC: | iboverma, jross, lzhaldyb, mtoth, pematous | |
| Target Milestone: | 3.0 | Keywords: | OtherQA | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | python-qpid-0.22-12 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1098314 (view as bug list) | Environment: | ||
| Last Closed: | 2014-09-24 15:10:25 UTC | 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: | 1098314 | |||
Fix available upstream if required/desired: https://svn.apache.org/r1571459 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1296.html |
Description of problem: Unlike the c++ client, you can't specify the node type in the address to override which is used. The queue is always prefered, so once a queue is created with the same name as an exchange, the python qpid.messaging client is prevented from publishing to that exchange. Version-Release number of selected component (if applicable): Anything up to and including qpid 0.26 How reproducible: 100% Steps to Reproduce: 1. qpid-config add queue foo 2. qpid-config add exchange fanout foo 3. qpid-config add queue q 4. qpid-config bind foo q (note this is the python version of spout and drain!) 5. spout 'foo; {node:{type:topic}}' a 6. spout 'foo' b 7. drain q 8. drain foo Actual results: Both a and b are received from foo in step 8, step 7 returns nothing. Expected results: Message a is returned in step 7, message b is returned in step 8. Additional info: