Page History

...

Running the Qpid Broker on Linux/Unix

• First set the QPID_HOME variable to reflect the root of your installation. For example, if you have installed the broker package into a directory <homedir>/broker/qpid-xx then you should set the QPID_HOME variable to <homedir>/broker/qpid-xx.

Then run the qpid-server script from the root dir of your install.

• You can also set the QPID_WORK variable in order to control the destination directory for the log dir into which broker logging is generated. For example, if you wish to set the working directory to be <homedir>/working you should set the QPID_WORK directory to be <homedir>/working.
• Note that the QPID_WORK variable defaults to the current user's home directory if not set.
• The config file supplied in the etc directory one level below your root dir probably doesn't need modification and is automatically picked up by the startup script
• Then run the qpid-server script from the root dir of your install. (The qpid-server script also supports cygwin environments.)

Command Line Arguments

You can get a list of all command line arguments by using the -h argument.

In particular, -p overrides the port specified in the config file and -b overrides the bind interface (default is wildcard).The qpid-server script also supports cygwin environments.

Checking the broker has started up

You can check that the broker has started up successfully by viewing the output it sends to stdout and looking for the start up port info:
2006-07-06 09:18:24,264 INFO  \[main\] server.Main (Main.java:181) - Starting Qpid.AMQP broker
2006-07-06 09:18:24,331 INFO  \[main\] server.Main (Main.java:251) - Qpid.AMQP listening on non-SSL address 0.0.0.0/0.0.0.0:5672

Note that you may have to edit the log4j.xml in the /etc directory to add an appender for the server.Main class to see loggeds output like this on startup.

Running the Qpid Broker on Windows

...