Bug 1098314
Summary: | Can't disambiguate name for which both queue and exchange exist | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Mike Cressman <mcressma> |
Component: | python-qpid | Assignee: | Mike Cressman <mcressma> |
Status: | CLOSED ERRATA | QA Contact: | Leonid Zhaldybin <lzhaldyb> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 2.3 | CC: | esammons, gsim, iboverma, jross, jwulf, lzhaldyb, pematous |
Target Milestone: | 2.5.1 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-qpid-0.18-11 | Doc Type: | Bug Fix |
Doc Text: |
A queue with the same name as an exchange made the exchange inaccessible to the python client. With this release, the python client now reliably sends to either a queue or exchange when they share the same name. The queue is preferred by default, and the exchange is indicated by specifying that the node type is topic, like so: <code>spout 'foo; {node:{type:topic}}'
|
Story Points: | --- |
Clone Of: | 1069757 | Environment: | |
Last Closed: | 2014-06-30 10:26:22 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: | 1069757 | ||
Bug Blocks: |
Comment 2
Leonid Zhaldybin
2014-05-29 13:27:46 UTC
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/RHBA-2014-0804.html |