Qpid supports AMQP 0-10, and some components also support the newest OASIS AMQP 1.0 standard and/or earlier AMQP 0-8/0-9/0-91 versions. The Java Broker and Client provide protocol negotiation. For details on cross component compatibility among releases, see: AMQP Release Compatibility for Qpid
If you have any questions about these releases, please email the user list
When you select a download you will be directed to a list of suggested mirrors for the file. If you encounter a problem with any mirror, please select another. If all mirrors are failing, there are backup mirrors at the end of the list that should be available, or you may also consult the complete list of mirrors.
Latest Release: 0.20
The release notes are available here: Release Notes
Individual PGP signatures are provided below, and the sha1sum output for each artefact is listed here: SHA1SUM.
Multiple Component Packages
|Full source release||qpid-0.20.tar.gz [PGP]||Y||Y||Y*|
|C++ broker & client||qpid-cpp-0.20.tar.gz [PGP]||Y||Y|
|Java broker, client & tools||qpid-java-0.20.tar.gz [PGP]||Y||Y||E*|
|All released artefacts||/qpid/0.20/||Y||Y||Y*|
|C# (.NET, WCF) WCF channel (C++ Broker Compatible)||qpid-wcf-0.20.zip [PGP]||Y|
|Java (AMQP 0-8/9/91/10)||qpid-java-client-0.20.tar.gz [PGP]||Y||Y|
|Java (AMQP 1.0)||qpid-java-amqp-1-0-client-jms-0.20.tar.gz [PGP]||Y|
C++ broker management
|Command-line tools||qpid-tools-0.20.tar.gz [PGP]||Y|
|QMF APIs||qpid-qmf-0.20.tar.gz [PGP]||Y|
* The AMQP 1.0 implementation in the Java broker is currently experimental.
The Java clients are also available via the Maven central repository. The following dependencies can be added to the POM for your maven build:
AMQP 0-8/9/91/10 Client:
AMQP 1.0 Client:
Additionally, you must provide the JMS API if it is not already available in your compilation and/or runtime environment, an example dependency for this would be:
Previous releases are available from http://archive.apache.org/dist/qpid/ .
QpidComponents.org provides further components for Apache Qpid, including both persistence and management tools. These components are open source, but are not developed as part of the Apache Qpid project due to licensing or other restrictions.
The Windows installer is available from http://www.riverace.com/qpid/downloads.htm. It is built from the C++ broker & client and C# WCF Channel source distributions listed above. It has been tested for Windows XP SP3 and above.
On Fedora, Qpid can be installed using yum. Because Java RPMs are not yet available in Fedora repos, the Java client is not in these distributions.
To install the server:
# yum install qpid-cpp-server
To install C++ and Python clients.
# yum install qpid-cpp-client-devel
# yum install python-qpid
The latest version of the code is always available in the source repository.
It is essential that you verify the integrity of the downloaded files using the PGP signatures or SHA1 checksums.
The PGP signatures can be verified using PGP or GPG. First download the KEYS file as well as the
.asc PGP signature file for the relevant artefact. Make sure you get these files from the relevant subdirectory of the main distribution directory, rather than from a mirror. Then verify the signatures using:
% pgpk -a KEYS
% pgpv qpid-0.20.tar.gz.asc
% pgp -ka KEYS
% pgp qpid-0.20.tar.gz.asc
% gpg --import KEYS
% gpg --verify qpid-0.20.tar.gz.asc
Alternatively, you can verify the SHA1 checksum of the files. A unix program called
sha1sum is included in many unix distributions. It is also available as part of GNU Textutils. For windows users, fsum supports SHA1. Ensure your generated checksum string matches the string published in the SHA1SUM file included with each release. Again, make sure you get this file from the relevant subdirectory of the main distribution directory, rather than from a mirror