Page History

1. What is Qpid ?

{cloak:q1}

The java implementation of Qpid is a pure Java message broker that implements the AMQP protocol. Essentially, Qpid is a robust, performant middleware component that can handle your messaging traffic. One of the most attractive aspects of Qpid is its cost - there is no licensing cost  !

...

• 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)

{cloak}

Can you help me get started with Qpid?

...

Here is a donated Spring configuration file appContext.zip which shows the config for Qpid side by side with Weblogic. HtH !

How do I configure the logging level for Qpid ?

The system property

amqj.logging.level

can be used to configure the logging level.

For the broker, you can use the environment variable AMQJ_LOGGING_LEVEL which is picked up by the qpid-run script (called by qpid-server to start the broker) at runtime.

For client code that you've written, simply pass in a system property to your command line to set it to the level you'd like i.e.

-Damqj.logging.level=INFO

The log level for the broker defaults to INFO if the env variable is not set, but you may find that your log4j properties affect this. Setting the property noted above should address this.

How can I configure the broker ?

...