Skip to main content

RabbitMQ Java Client 5.0 is Released

· 3 min read

The RabbitMQ team is happy to announce the release of version 5.0 of the RabbitMQ Java Client. This new release is now based on Java 8 and comes with a bunch of interesting new features.

Java 8 is Now a Pre-requisite

RabbitMQ Java Client has been supporting Java 6 (released in 2006!) for many years. It was time to bump the pre-requisites to benefit from modern Java features. No need to worry for those stuck on Java 6 or Java 7: we will support Java Client 4.x.x series for the next upcoming months (bug fixes and even relevant new features if possible). Note the Java Client 5.0 (as well as 4.x.x) also supports Java 9.

Spring Cleaning

Some classes and interfaces showed to be less relevant these days and were marked as deprecated in the previous major versions: this is the case of FlowListener and QueueingConsumer (among others). They have been removed in 5.0.

New Lambda-oriented Methods

Lambda-oriented methods have been introduced for common use cases, e.g. to consume a message:

(consumerTag, delivery) -> businessService.handle(delivery),
consumerTag ->"Consumer {} has been cancelled")

Other lambda-oriented methods are also available for most of the client listeners. This should make relevant application code more concise and readable.

More Flexibility to Specify Client Certificate

In Java, a client certificate is presented through a SSLContext's KeyManager. If different client connections needed different client certificates in the RabbitMQ Java Client, they needed different instances of ConnectionFactory. In 5.0, we introduced the SslContextFactory:

public interface SslContextFactory {

SSLContext create(String name);


You can now set your own SslContextFactory in the ConnectionFactory to provide the logic based on the connection name to create the appropriate SslContext for this connection. The SslContextFactory implementation can look up certificates from a file system directory or from any other certificate repository (database, LDAP registry, etc). Combined with NIO (added in 4.0), this is a great way to have many client connections in a single JVM process that uses only a few threads.

Breaking Changes

A major release is a good time to do some cleaning as seen above and to introduce new features. Unfortunately, those new features sometimes break existing API. Cheer up, as we strived to maintain backward compatibility and most applications shouldn't be impacted by those changes. If in doubt, check the dedicated section in the release change log.

Wrapping Up

The RabbitMQ team hopes you'll enjoy this new version of the Java Client. Don't hesitate to consult the release change log for all the details. The binaries are available as usual from Maven Central and from our Bintray repository. To use RabbitMQ Java Client 5.0, add the following dependency if you're using Maven:


If you're using Gradle:

compile 'com.rabbitmq:amqp-client:5.0.0'