[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312049#comment-16312049
]
Alan Conway commented on DISPATCH-878:
--------------------------------------
Fixed PROTON-1706. You can now get the list of real addresses used by a
listener once it is open (at the PN_LISTENER_OPEN event)
To print all the listening addresses do something like:
{code}
pn_netaddr_t *na = pn_netaddr_listening(my_listener);
while (na) {
char str[PN_MAX_ADDR] = "";
pn_netaddr_str(na, str, sizeof(str));
log_this_somewhere(str); // Contains bare "host:port"
na = pn_netaddr_next(na);
}
{code}
> 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
>
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
