[jira] [Commented] (DISPATCH-1428) route connection not indexed by 'connection' field of connector

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DISPATCH-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933549#comment-16933549 ] 

ASF GitHub Bot commented on DISPATCH-1428:
------------------------------------------

grs commented on pull request #567: DISPATCH-1428
URL: https://github.com/apache/qpid-dispatch/pull/567
 
 
   Allow a route-container connection to be looked up by connector name, even if the container id is the same as a connection from a different connector.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> route connection not indexed by 'connection' field of connector
> ---------------------------------------------------------------
>
>                 Key: DISPATCH-1428
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1428
>             Project: Qpid Dispatch
>          Issue Type: Bug
>            Reporter: Gordon Sim
>            Priority: Major
>
> The connection established by a route-container connector will not be indexed by the 'connection' field of that connector if there is already an existing route-connection with the same container id but established by a different connector.
> E.g. start router on 5672 and a broker (or a separate router emulating a broker) on 5673, then:
> {noformat}
> for n in foo bar; do
>     qdmanage CREATE --type connector --name $n role=route-container host=localhost port=5673; 
>     qdmanage CREATE --type linkRoute --name $n pattern=$n direction=in connection=$n;
> done;
> qdstat --linkroute
> {noformat}
> Only one of these link routes is active though both connections are established.
> The issues is that when the first connection is established, it indexes the qdr_conn_identifier_t by container-id and the connection label from the connector. When the second connection is established, it looks up first by container id, so adds itself to the qdr_conn_identifier_t created by the first connection. There is then no entry in the index for the connection label of the second connector, so the second link route can never be activated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org