qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
Date Fri, 01 Dec 2017 15:56:00 GMT

    [ https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274549#comment-16274549
] 

Jeremy commented on DISPATCH-878:
---------------------------------

[~aconway] Indeed, I'm aware of that. 
I did not clarify what I meant by a  "reliable" way of getting the port, however, the multiple
ports scenario fits in (although we're not using it right now).
Furthermore, on windows, it's hackier to get the port (although we do not currently launch
the dispatch router on windows, we are considering it for testing locally on dev machines).
In fact, for my case right now, I can launch qdrouterd and get its pid which would give me
access to its port as you mentioned. Therefore, if you want to close this issue, I don't mind.

[~ganeshmurthy] Indeed that's what I was expecting. This ways I can do a small grep to get
the port.


> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message