[
https://issues.apache.org/jira/browse/DISPATCH-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated DISPATCH-1428:
---------------------------------
Description:
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 one router on port 5673, another (not part of same router network)
on 5672 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.
was:
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 one router on port 5673, another on 5672 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.
> 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 one router on port 5673, another (not part of same router network)
> on 5672 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
