Bug 694226
| Summary: | Node bindings not established correctly when address used for producer | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Rajith Attapattu <rattapat+nobody> |
| Component: | qpid-java | Assignee: | Rajith Attapattu <rattapat+nobody> |
| Status: | CLOSED DUPLICATE | QA Contact: | Petr Matousek <pematous> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | Development | CC: | jross, pematous, tross |
| Target Milestone: | 3.0 | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-27 10:52:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This is tracked in upstream via QPID-3182 This is fixed in Qpid trunk http://svn.apache.org/viewvc?view=rev&rev=1089552 Fixed prior to the 0.14 rebase Issue fixed, tested on rhel5.8 / 6.2 i/x on packages: qpid-java-0.14-3.el5 qpid-java-0.14-3.el6 CLOSED/CRELEASE -> ASSIGNED -> ON_QA -> VERIFIED This issue is NOT fixed. The originally reported issue in Comment 0 is fixed, but assume a following case: # qpid-config add queue q # ./run_example.sh org.apache.qpid.example.Spout "ex/key;{ create: always, node: { type: topic, x-bindings: [{ exchange:'ex', queue: 'q', key: 'key' }]}}" The result is exactly the same as originally reported issue, the binding is not established when Spout client is used. Drain doesn't suffer from that. tested on rhel5.8 / 6.2 i/x on packages: qpid-java-0.14-3.el5 qpid-java-0.14-3.el6 -> ASSIGNED note: This issue is also a part of Bug 726687, expected behaviour can be seen in 'Additional info' in c0 of that bug. A fix has been made in upstream http://svn.apache.org/viewvc?rev=1397651&view=rev You could use the test specified in 694226#c4 to verify this issue. *** This bug has been marked as a duplicate of bug 726687 *** |
Description of problem: The behaviour in resolving addresses in JMS client appears to vary by context. Consider the following address: "my-queue; {create:always, node:{x-bindings:[{ exchange:'amq.fanout', queue:'my-queue'}]}}" This should result in a queue named my-queue being created and in that queue being bound to the amq.fanout exchange. This is indeed the case if the address is passed to the Drain example. However when passed to the Spout example, the queue is created but the binding is not established. Version-Release number of selected component (if applicable): qpid-java-0.10-2 and below How reproducible: Always Steps to Reproduce: 1. Use above address with the java version of Spout 2. Observe that the bindings are not created. Actual results: Bindings are not created for the queue. Expected results: Bindings should be created for the queue. Additional info: