You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Olivier VERMEULEN (JIRA)" <ji...@apache.org> on 2018/11/07 13:33:00 UTC

[jira] [Comment Edited] (DISPATCH-1172) Link routes and auto links activated on wrong connections if many route-container conns exist

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

Olivier VERMEULEN edited comment on DISPATCH-1172 at 11/7/18 1:32 PM:
----------------------------------------------------------------------

[~ganeshmurthy] In case of multiple route-container connections what kind of issues could I face?

I'm asking because we are facing a random issue right now where a message sent to a topic (through a dispatch-router configured with multiple route-container connections) is being routed to the DLQ instead of the queue matching its binding-key... Could it come from this?


was (Author: overmeulen):
In case of multiple route-container connections what kind of issues could I face?

I'm asking because we are facing a random issue right now where a message sent to a topic (through a dispatch-router configured with **multiple route-container connections) is being routed to the DLQ instead of the queue matching its binding-key... Could it come from this?

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org