[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16268982#comment-16268982
]
Jeremy edited comment on DISPATCH-878 at 11/28/17 4:17 PM:
-----------------------------------------------------------
Indeed, at Murex, we use the qpid _java_ broker and it has this feature.
We were testing with the qpid dispatch router to see if it supports being
launched on port 0, and we saw that it was supported. However, we have no
(reliable) way to tell what port it is actually using. This makes the feature
half supported :)
This feature is interesting for us, because we want to launch several dispatch
routers, and we would benefit from the following:
- Having a single configuration for the port is simpler for us
- Avoid having an error that the port is already taken, which would simplify
the life of the cluster operator
was (Author: jeremy.aouad):
Indeed, at Murex, we use the qpid _java _broker and it has this feature.
We were testing with the qpid dispatch router to see if it supports being
launched on port 0, and we saw that it was supported. However, we have no
(reliable) way to tell what port it is actually using. This makes the feature
half supported :)
This feature is interesting for us, because we want to launch several dispatch
routers, and we would benefit from the following:
- Having a single configuration for the port is simpler for us
- Avoid having an error that the port is already taken, which would simplify
the life of the cluster operator
> 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]
