[
https://issues.apache.org/jira/browse/QPID-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502548
]
Alan Conway commented on QPID-504:
----------------------------------
qpidd prints log messages to a configurable destination: stderr, file or
syslog. However --print-port or suchlike options are exceptions and print to
stdout. It's only likely to be used for development/debugging so it's not a
problem.
> Both the C and Java brokers should behave in the same way and accept the same
> command line options (where that makes sense).
A fine aspiration, but it won't happen without significant effort on both
sides. The easiest way to do things in each language is very different. qpidd
uses boost::program_options for command line and config file parsing. It is
farily flexbile if we ever do sit down and agree on this stuff.
> 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
>
> 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.
