[
https://issues.apache.org/jira/browse/QPID-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504234
]
Alan Conway commented on QPID-504:
----------------------------------
The C++ broker now works as follows: qpidd --daemon --port 0 binds to an
available port (selected by the OS) and prints the bound port. There's no
explicit --print-port, if the requested port is 0 the actual bound port is
always printed. This solves both problems mentioned above.
This JIRA remains open because the C++ tests need to be reworked to accept the
broker port in a consistent way. I suggest they use the same option parser used
by qpidd, so that they can accept either a --port option or a QPID_PORT
environment variable. The latter makes things particularly easy for test
scripts:
export QPID_PORT=`qpidd -dp0`
run_clients # No extra flags needed if clients use QPID_PORT env var.
> 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.
