Downloads

Qpid supports the latest version of AMQP 0-10, and some components also the earlier AMQP 0-8 and 0-9 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.

It is good practice to verify the integrity of the downloaded files using signatures downloaded from our main distribution directory.

Latest Release: 0.18

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

Component	Download	AMQP 0-10	AMQP 0-8/0-9
Full source release	qpid-0.18.tar.gz [PGP]	Y	Y
C++ broker & client	qpid-cpp-0.18.tar.gz [PGP]	Y
Java broker, client & tools	qpid-java-0.18.tar.gz [PGP]	Y	Y
All released artefacts	/qpid/0.18/	Y	Y

Single Component Packages

Broker

Language	Download	AMQP 0-10	AMQP 0-8/0-9
Java	qpid-java-broker-0.18.tar.gz [PGP]	Y	Y

Client

Language	Download	AMQP 0-10	AMQP 0-8/0-9
C# (.NET, WCF) WCF channel (C++ Broker Compatible)	qpid-wcf-0.18.zip [PGP]	Y
Java	qpid-java-client-0.18.tar.gz [PGP]	Y	Y
Python	qpid-python-0.18.tar.gz [PGP]	Y	Y

Management tools

C++ broker management

Component	Download	AMQP 0-10	AMQP 0-8/0-9
Command-line tools	qpid-tools-0.18.tar.gz [PGP]	Y
QMF APIs	qpid-qmf-0.18.tar.gz [PGP]	Y

Java broker management

Component	Download
JMX Management Console	Linux x86 [PGP] \| Linux x86_64 [PGP] \| Mac OS X [PGP] \| Solaris 10 Sparc [PGP] \| Windows x86 [PGP]

Maven artifacts

The Java client is also available via the Maven central repository. To use the client in your Maven build you should add the following dependency to your POM:


        <dependency>

          <groupId>org.apache.qpid</groupId>

          <artifactId>qpid-client</artifactId>

          <version>0.18</version>

        </dependency>

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:


        <dependency>

          <groupId>org.apache.geronimo.specs</groupId>

          <artifactId>geronimo-jms_1.1_spec</artifactId>

          <version>1.0</version>

        </dependency>

Previous Releases

Previous releases are available from http://archive.apache.org/dist/qpid/ .

QpidComponents.org

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.

Contributed C++ Packages

Windows Installer

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.

Pre-built Linux Packages

Fedora

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 qpidd

To install C++ and Python clients:

        # yum install qpidc-devel

        # yum install amqp python-qpid

To install documentation:

        # yum install rhm-docs

To install persistence using an external store module:

        # yum install rhm

Source Code Repository

The latest version of the code is always available in the source repository.

Verify the integrity of the files

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.18.tar.gz.asc or
% pgp -ka KEYS % pgp qpid-0.18.tar.gz.asc or
% gpg --import KEYS % gpg --verify qpid-0.18.tar.gz.asc

Alternatively, you can verify the SHA1 checksum of the files. A unix program called sha1 or 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