[
https://issues.apache.org/jira/browse/QPID-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504008
]
Nuno Santos commented on QPID-504:
----------------------------------
To clarify my comment above, having the option to output the bound port upon
request (ie, having the command line option --print-port) is not enough for the
purposes of testing because it does not address the possibility of having more
than one broker running at the same time. Say within the context of a test
suite / automated build, you start a broker instance, and then call
--print-port... if there was already another broker running, which one will
respond?
I think we need to provide a mechanism similar to what John was referring to
above, where the broker prints the bound port upon start-up (which can then be
grabbed by whoever starts a specific instance of the broker). This can be in
addition to --print-port.
> Dynamic port for automated tests.
> ---------------------------------
>
> Key: QPID-504
> URL: https://issues.apache.org/jira/browse/QPID-504
> Project: Qpid
> Issue Type: Test
> Components: C++ Broker
> Reporter: Alan Conway
> Assignee: Alan Conway
>
> As development ramps up we will have multiple qpid builds on the same machine
> clashing for use of the AMQP default port.
> All automated tests should use a *dynamically assigned* (i.e. bind(0)) port.
> Allowing a manually specified port number for tests doesn't solve the problem
> as there's no way to choose
> a port that is guaranteed not to be used by any other test on the same host.
> One way to do this:
> - add qpidd --print-port option to print the actual bound port
> - add qpid option processing to qpid client library, enable in all test
> programs.
> - test harness does "qpidd --daemon --port 0 --print-port" and sets the
> printed port to QPID_PORT in env for all test clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
