You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2016/04/06 00:06:25 UTC
[jira] [Created] (DISPATCH-261) Bind error on one port causes bind
error on other ports
Chuck Rolke created DISPATCH-261:
------------------------------------
Summary: 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
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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org