[
https://issues.apache.org/jira/browse/DISPATCH-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677191#comment-16677191
]
Ganesh Murthy commented on DISPATCH-1172:
-----------------------------------------
Dispatch uses a qdr_conn_identifier_t to aggregate connection ref objects.
These conn identifier objects are used to identify connections on which link
routers and auto links are to be activated. Connectors are identified by a name
and this name is referenced by link routes and auto links. A few releases ago,
we started allowing container ids to be specified on link routes and auto
links. Multiple connections can be made to a container and the code was
modified to allow this to happen but the code is incomplete. Consider creating
many connections using the dollowing -
{noformat}
for i in {1..10}; do
qdmanage -b 0.0.0.0:5673 create --type org.apache.qpid.dispatch.connector
host=0.0.0.0 port=5672 name=broker_conn${i} role=route-container
done{noformat}
all the connections created are aggregated under one container id. In addition
to doing this, these connections must also have their own connection identifier
object which is not happening right now. As a result, link routes and auto
links get activated on the wrong connections.
If you have only one route-container connection between router and broker,
there should be no issues.
Connection trunking is being looked at as a new feature to be added to the
router. This feature will be fixed as part of that feature.
> Link routes and auto links activated on wrong connections if many
> route-container conns exist
> ---------------------------------------------------------------------------------------------
>
> Key: DISPATCH-1172
> URL: https://issues.apache.org/jira/browse/DISPATCH-1172
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 1.4.1
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
> Priority: Major
>
> Run the following script
>
> {noformat}
> #!/usr/bin/env bash
> qdmanage -b 0.0.0.0:5673 create --type
> org.apache.qpid.dispatch.router.config.address prefix=dest waypoint=true
> qdmanage -b 0.0.0.0:5673 create --type
> org.apache.qpid.dispatch.router.config.address prefix=sub waypoint=true
> for i in {1..10}; do
> qdmanage -b 0.0.0.0:5673 create --type org.apache.qpid.dispatch.connector
> host=0.0.0.0 port=5672 name=broker_conn${i} role=route-container
> done
> for i in {1..10}; do
> qdmanage -b 0.0.0.0:5673 create --type
> org.apache.qpid.dispatch.router.config.autoLink addr=dest direction=out
> name=auto-link-dest${i} connection=broker_conn${i}
> done
> for i in {1..10}; do
> qdmanage -b 0.0.0.0:5673 create --type
> org.apache.qpid.dispatch.router.config.autoLink addr=sub direction=in
> name=auto-link-sub${i} connection=broker_conn${i}
> done{noformat}
>
> all auto links will be activated against all connections. This happens also
> with link routes.
>
> This problem happens due to the way the connections are aggregated under a
> single container id. The connections should also get their own connection ids.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
