You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org> on 2008/01/16 15:42:37 UTC

[jira] Created: (QPID-739) When using an AMQP destination, the queue routing key is not set correctly

When using an AMQP destination, the queue routing key is not set correctly 
---------------------------------------------------------------------------

                 Key: QPID-739
                 URL: https://issues.apache.org/jira/browse/QPID-739
             Project: Qpid
          Issue Type: Bug
          Components: Java Client
    Affects Versions: M3
            Reporter: Arnaud Simon
             Fix For: M3


When a destination is looked up from JNDI, the queue name is used as routing key when it should be the destination name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (QPID-739) When using an AMQP destination, the queue routing key is not set correctly

Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajith Attapattu reopened QPID-739:
-----------------------------------

      Assignee: Rajith Attapattu

The current fix is not correct due to the following reasons.
The binding URL is defined as follows.
<exch_class>://<exch_name>/[<destination>]/[<queue>]?<option>='<value>'[,<option>='<value>']*
RoutingKey is given as a valid option (See BindingURL class). See documentation link
http://cwiki.apache.org/qpid/bindingurlformat.html
Therefore returning the destinationName as the routing key is wrong.

In AMQDestination, destinationName is used as the routingKey which is creating confusion and it is also semantically wrong.
The field destinationName should refer to the exchange we are publishing. But we already have a field named "exchangeName".
Therefore the destinationName should be renamed to routingKey.

> When using an AMQP destination, the queue routing key is not set correctly 
> ---------------------------------------------------------------------------
>
>                 Key: QPID-739
>                 URL: https://issues.apache.org/jira/browse/QPID-739
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Arnaud Simon
>            Assignee: Rajith Attapattu
>             Fix For: M3
>
>
> When a destination is looked up from JNDI, the queue name is used as routing key when it should be the destination name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (QPID-739) When using an AMQP destination, the queue routing key is not set correctly

Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajith Attapattu resolved QPID-739.
-----------------------------------

    Resolution: Won't Fix

See https://issues.apache.org/jira/browse/QPID-741 for more details.

> When using an AMQP destination, the queue routing key is not set correctly 
> ---------------------------------------------------------------------------
>
>                 Key: QPID-739
>                 URL: https://issues.apache.org/jira/browse/QPID-739
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Arnaud Simon
>            Assignee: Rajith Attapattu
>             Fix For: M4
>
>
> When a destination is looked up from JNDI, the queue name is used as routing key when it should be the destination name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Resolved: (QPID-739) When using an AMQP destination, the queue routing key is not set correctly

Posted by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Simon resolved QPID-739.
-------------------------------

    Resolution: Fixed

I have changed the getRoutingKey of AMQQeue for returning the destination name if set. 

> When using an AMQP destination, the queue routing key is not set correctly 
> ---------------------------------------------------------------------------
>
>                 Key: QPID-739
>                 URL: https://issues.apache.org/jira/browse/QPID-739
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Arnaud Simon
>             Fix For: M3
>
>
> When a destination is looked up from JNDI, the queue name is used as routing key when it should be the destination name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (QPID-739) When using an AMQP destination, the queue routing key is not set correctly

Posted by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Simon closed QPID-739.
-----------------------------


> When using an AMQP destination, the queue routing key is not set correctly 
> ---------------------------------------------------------------------------
>
>                 Key: QPID-739
>                 URL: https://issues.apache.org/jira/browse/QPID-739
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Arnaud Simon
>             Fix For: M3
>
>
> When a destination is looked up from JNDI, the queue name is used as routing key when it should be the destination name. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.