You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2011/04/04 13:13:07 UTC
[jira] [Created] (QPID-3182) node bindings not established
correctly when address used for producer
node bindings not established correctly when address used for producer
----------------------------------------------------------------------
Key: QPID-3182
URL: https://issues.apache.org/jira/browse/QPID-3182
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.10
Reporter: Gordon Sim
Assignee: Rajith Attapattu
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Resolved] (QPID-3182) node bindings not established
correctly when address used for producer
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-3182.
------------------------------------
Resolution: Fixed
Fixed with a test case.
> node bindings not established correctly when address used for producer
> ----------------------------------------------------------------------
>
> Key: QPID-3182
> URL: https://issues.apache.org/jira/browse/QPID-3182
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.10
> Reporter: Gordon Sim
> Assignee: Rajith Attapattu
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Issue Comment Edited] (QPID-3182) node bindings not
established correctly when address used for producer
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015974#comment-13015974 ]
Rajith Attapattu edited comment on QPID-3182 at 4/6/11 6:05 PM:
----------------------------------------------------------------
This is not a regression, rather a bug that has been there for a while.
This bug is due to the address resolution code not issuing a queue-bind after it creates the queue.
The above address works as expected for consumers bcos to the registerConsumer method in AMQSession.java invokes the bindQueue method for both addressing and binding URL based destinations, therefore compensating for the above mistake.
was (Author: rajith):
This is not regression, rather due to a bug that has been there for a while.
This bug is due to the address resolution code not issuing a queue-bind after it creates the queue.
The above address works as expected for consumers due to the registerConsumer method in AMQSession.java invokes the bindQueue method for both addressing and binding URL based destinations, hence compensating for the above mistake.
> node bindings not established correctly when address used for producer
> ----------------------------------------------------------------------
>
> Key: QPID-3182
> URL: https://issues.apache.org/jira/browse/QPID-3182
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.10
> Reporter: Gordon Sim
> Assignee: Rajith Attapattu
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Commented] (QPID-3182) node bindings not established
correctly when address used for producer
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015974#comment-13015974 ]
Rajith Attapattu commented on QPID-3182:
----------------------------------------
This is not regression, rather due to a bug that has been there for a while.
This bug is due to the address resolution code not issuing a queue-bind after it creates the queue.
The above address works as expected for consumers due to the registerConsumer method in AMQSession.java invokes the bindQueue method for both addressing and binding URL based destinations, hence compensating for the above mistake.
> node bindings not established correctly when address used for producer
> ----------------------------------------------------------------------
>
> Key: QPID-3182
> URL: https://issues.apache.org/jira/browse/QPID-3182
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.10
> Reporter: Gordon Sim
> Assignee: Rajith Attapattu
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org