[
https://issues.apache.org/jira/browse/DISPATCH-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross closed DISPATCH-252.
-----------------------------
Resolution: Won't Fix
As Ganesh points out, preventing the router from connecting to itself is
actually complicated. Though this is clearly a misconfiguration, I'm not aware
of a significant downside to allowing this misconfiguration. This is a
won't-fix for now.
> 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: Ted Ross
>
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
