[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16268921#comment-16268921
]
Ganesh Murthy edited comment on DISPATCH-878 at 11/28/17 3:31 PM:
------------------------------------------------------------------
Jeremy, can you please explain why you need this change. We have had tried to
do this in other projects and found that it adds a lot of complication and
future bugs. It would be best not to put this feature in.
was (Author: ganeshmurthy):
Jeremy, can you please explain why you need this change. We have had tried to
do this in other projects and it found that it adds a lot of complication and
future bugs. It would be best not to put this feature in.
> 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: [email protected]
For additional commands, e-mail: [email protected]
