[
https://issues.apache.org/jira/browse/DISPATCH-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224353#comment-15224353
]
Ganesh Murthy commented on DISPATCH-252:
----------------------------------------
I looked into a bit on how to implement this. The addr/port (e.g.
127.0.0.1/23455) combination must be tested for uniqueness across listeners and
connectors. But the code gets a bit complicated because the addr in a connector
can be set to 127.0.0.1 and the connector could have addr set to 0.0.0.0 or
localhost and all these combinations should be treated equally.
Ted, can you please add your thoughts?
> Router should disallow creation of a connector port that already has a
> listener
> -------------------------------------------------------------------------------
>
> Key: DISPATCH-252
> URL: https://issues.apache.org/jira/browse/DISPATCH-252
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Reporter: Chuck Rolke
> Assignee: Ganesh Murthy
>
> From DISPATCH-250
> The router allows management to create a connector on top of a listener.
> {noformat}
> checkout and build a clean copy of qpid-dispatch
> edit the config file in qpid-dispatch/etc/ by adding a new listener:
> listener { addr: 0.0.0.0 port: 20102 }
> start the router
> create a new connector using the listener's port
> qdmanage CREATE --type connector port=20102 name=myconn
> delete the new connector by name two times
> qdmanage DELETE --type connector --name myconn
> qdmanage DELETE --type connector --name myconn
> {noformat}
> The report in DISPATCH-250 exposed a crash which has been fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
