[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327584#comment-16327584
]
Ganesh Murthy commented on DISPATCH-878:
----------------------------------------
If you want to have two listeners on port: 0, give those listeners different
names. For example -
{noformat}
listener {
name: listener1
host: 0.0.0.0
port: 0
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
listener {
name: listener2
host: 0.0.0.0
port: 0
authenticatePeer: no
saslMechanisms: ANONYMOUS
}{noformat}
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> -------------------------------------------------------------------------------------------------------
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
> Reporter: Jeremy
> Assignee: Ganesh Murthy
> Priority: Major
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
