Page History

...

*High performance header-based routing for messages
*Most features required by the JMS 1.1 specification. See our roadmap for details of missing JMS features and when we expect to add them.
*Transaction support
*Persistence using the high performance Berkeley DB Java Edition. The persistence layer is also pluggable should an alternative implementation be required.
*Pluggable security using SASL. Any Java SASL provider should be capable of working with Blaze.
*Management using JMX and MC4J (again see our roadmap for details of this feature and our future plans in this area)
*Clustering for scalability
*.NET API implementation (currently an alpha release; see our roadmap)

How do I contact the Qpid team ?

tbc

Can you help me get started with Qpid?

...

For more detailed information on configuration, please see our Qpid Configuration Page.

How can I change the port the broker uses at runtime ?

...

For more detailed information on configuration, please see our Qpid Configuration Page.

What command line options can I pass into the qpid-server script ?

...

For more detailed information on configuration, please see our Qpid Configuration pagePage.

How do I authenticate with the broker ? What user id & password should I use ?

...

You can then pass this amended config.xml into the broker at startup using the -c flag i.e.
qpid-server -c <path>/config.xml

How do I contact the Qpid team ?

tbc