[
https://issues.apache.org/jira/browse/DISPATCH-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246441#comment-15246441
]
ASF GitHub Bot commented on DISPATCH-261:
-----------------------------------------
GitHub user ganeshmurthy opened a pull request:
https://github.com/apache/qpid-dispatch/pull/65
DISPATCH-261 - Added a new field called state to qd_config_listener_t…
… so it can be checked before activating listeners
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-261
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/65.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #65
----
commit ad1cb4aafcc411c34a3dd60eabef91a9494efd75
Author: Ganesh Murthy <[email protected]>
Date: 2016-04-18T20:10:28Z
DISPATCH-261 - Added a new field called state to qd_config_listener_t so it
can be checked before activating listeners
----
> Bind error on one port causes bind error on other ports
> -------------------------------------------------------
>
> Key: DISPATCH-261
> URL: https://issues.apache.org/jira/browse/DISPATCH-261
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Chuck Rolke
> Assignee: Ganesh Murthy
>
> Run a service, like an AMQP broker, on port 5672.
> Start Dispatch Router with config
> {noformat}
> listener {
> addr: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> listener {
> addr: 0.0.0.0
> port: 20102
> }
> {noformat}
> The router reports:
> {noformat}
> Tue Apr 5 17:55:04 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp
> proto=any role=normal
> Tue Apr 5 17:55:04 2016 DRIVER (error) bind: Address already in use
> Tue Apr 5 17:55:04 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20102
> proto=any role=normal
> Tue Apr 5 17:55:04 2016 DRIVER (error) bind: Address already in use
> {noformat}
> The error on port 5672 is correct. The error on port 20102 is bogus. There is
> no conflict on that port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
