On 01/17/2011 03:38 PM, mick wrote:
On Mon, 2011-01-17 at 14:27 -0500, Alan Conway wrote:
On 01/17/2011 01:44 PM, mick wrote:
On Mon, 2011-01-17 at 14:57 +0000, Gordon Sim wrote:
On 01/17/2011 02:57 PM, Alan Conway wrote:
I suggest the following, which I've seen used to good effect in previous
projects:
--dump-config FILE Instruct the broker to write it's configuration to
FILE (default none)
This would write a file in the known qpid-config file format with the
"live" values of config items like port or ssl-port, or other computed
config values.
When config can be picked up from multiple sources, such a tool is
useful to be sure what actually got configured. It uses existing known
file formats. It clearly scopes the use of the tool to checking initial
configuration, it doesn't want to become a replacement for management.
I like that!
sounds good, as long as the ssl port is actually chosen by the time we
have to dump this out. i'll have to look at that.
no intention of making this a management-replacement, not even 'lite'.
write-only by the brokers.
i would still see this going to a standard place ,
i.e. /var/lib/qpid/PID -- using the pid just to prevent collisions.
and then remove file on healthy shutdown.
I think this is a useful feature for debugging etc. but I don't think it should
be done by default. If the user wants this let them specify where they want it -
as we do with log files.
but the point was to be able to start up a script or some client after
the brokers have already started, and have a way of finding basic
connectivity info. if you don't put it in a standard place, it seems to
me that you defeat that purpose.
So start brokera with --dump-configuration=a.conf and broker b with
--dump-configuration=b.conf and write your test script to look at a.conf and
b.conf. We're talking about tests that run multiple brokers on the same box, so
we can easily decide what options to set on the brokers.
I don't see this as something that applies in deployment. You're never going to
deploy brokers without knowing in advance what port they're using, the broker's
host:port are the fundamental location information that clients have to know to
connect. I don't see any non-test use case where a client knows the broker's PID
but not the port.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
