5.1.1

Changes between 5.1.0 and 5.1.1

This is a patch release with a bug fix. It is compatible with 5.0.0 and 5.1.0. All users of the 5.x.x series are encouraged to upgrade to this version. Users of previous version should check the 5.0.0 changelog for breaking changes

Fix client version property file name

A warning log message was emitted because of a misnamed file.

GitHub issue: #335

4.4.1

Changes between 4.4.0 and 4.4.1

This is a patch release that includes a bug fix. This release is backward-compatible with 4.3.0. Users of the 3.6.x and 4.x.x series are encouraged to use this version.

Fix client version property file name

A warning log message was emitted because of a misnamed file.

GitHub issue: #335

5.1.0

Changes between 5.0.0 and 5.1.0

This maintenance release catches up with new features and bug fixes from 4.3.0 and 4.4.0. It is compatible with 5.0.0. All users of 5.0.0 are encouraged to upgrade to this version. Users of previous version should check the 5.0.0 changelog for breaking changes.

Add property file-based initialization

It's now possible to use a property file to configure the ConnectionFactory (e.g. host, username, password, etc).

GitHub issue: #324

Add Java 9 module name

The Automatic-Module-Name: com.rabbitmq.client entry has been added to the JAR manifest, for interoperability with JDK 9 module system.

GitHub issue: #320

Get rid of read retry in NIO

The NIO mode used to use retries on network reading to make sure the outstanding frame would be completed in the current loop iteration. It now handle partial frames and moves on if a frame cannot be completed immediately. This behaviour is more consistent with NIO usage.

GitHub issue: #319

Load client version in a more reliable way

This could affect classpath-sensitive environments like OSGi.

GitHub issue: #334

Support Micrometer

The Java Client supports Micrometer through its MicrometerMetricsCollector implementation of MetricsCollector. Micrometer is an instrumentation facade, which supports popular metrics backends (Atlas, Graphite, Ganglia, Datadog, JMX, etc). Note Micrometer requires Java 8 or more. The Java Client 4.3.x still supports Java 6, but Micrometer support isn't usable on Java 6 and Java 7.

GitHub issue: #313

Make auto-recovery retry interval calculation pluggable

The RecoveryDelayHandler interface has been introduced to calculate the retry interval between each connection recovery attempt. The default strategy is still the same: a constant interval (5 seconds by default). The ExponentialBackoffDelayHandler implementation can be used to have an exponential retry interval.

Thanks to @vikinghawk for this contribution.

GitHub issue: #308

Handle several buffer underflow results in SslEngineByteBufferInputStream

Thanks to @dimas for this fix.

GitHub issue: #317

4.4.0

Changes between 4.3.0 and 4.4.0

This is a maintenance release that includes 2 new features and 2 bug fixes. This release is backward-compatible with 4.3.0. Users of the 3.6.x and 4.x.x series are encouraged to use this version.

Add property file-based initialization

It's now possible to use a property file to configure the ConnectionFactory (e.g. host, username, password, etc).

GitHub issue: #324

Add Java 9 module name

The Automatic-Module-Name: com.rabbitmq.client entry has been added to the JAR manifest, for interoperability with JDK 9 module system.

GitHub issue: #320

Get rid of read retry in NIO

The NIO mode used to use retries on network reading to make sure the outstanding frame would be completed in the current loop iteration. It now handle partial frames and moves on if a frame cannot be completed immediately. This behaviour is more consistent with NIO usage.

GitHub issue: #319

Load client version in a more reliable way

This could affect classpath-sensitive environments like OSGi.

GitHub issue: #334

5.1.0.RC1

Changes between 5.0.0 and 5.1.0.RC1

This is a pre-release for 5.1.0, a maintenance release that catches up with new features and bug fixes from 4.3.0 and 4.4.0. It is compatible with 5.0.0. All users of 5.0.0 are encouraged to test this pre-release. Users of previous version should check the 5.0.0 changelog for breaking changes.

Add property file-based initialization

It's now possible to use a property file to configure the ConnectionFactory (e.g. host, username, password, etc).

GitHub issue: #324

Add Java 9 module name

The Automatic-Module-Name: com.rabbitmq.client entry has been added to the JAR manifest, for interoperability with JDK 9 module system.

GitHub issue: #320

Get rid of read retry in NIO

The NIO mode used to use retries on network reading to make sure the outstanding frame would be completed in the current loop iteration. It now handle partial frames and moves on if a frame cannot be completed immediately. This behaviour is more consistent with NIO usage.

GitHub issue: #319

Load client version in a more reliable way

This could affect classpath-sensitive environments like OSGi.

GitHub issue: #334

Support Micrometer

The Java Client supports Micrometer through its MicrometerMetricsCollector implementation of MetricsCollector. Micrometer is an instrumentation facade, which supports popular metrics backends (Atlas, Graphite, Ganglia, Datadog, JMX, etc). Note Micrometer requires Java 8 or more. The Java Client 4.3.x still supports Java 6, but Micrometer support isn't usable on Java 6 and Java 7.

GitHub issue: #313

Make auto-recovery retry interval calculation pluggable

The RecoveryDelayHandler interface has been introduced to calculate the retry interval between each connection recovery attempt. The default strategy is still the same: a constant interval (5 seconds by default). The ExponentialBackoffDelayHandler implementation can be used to have an exponential retry interval.

Thanks to @vikinghawk for this contribution.

GitHub issue: #308

Handle several buffer underflow results in SslEngineByteBufferInputStream

Thanks to @dimas for this fix.

GitHub issue: #317

4.4.0.RC2

Changes between 4.3.0 and 4.4.0.RC2

This is a release candidate for 4.4.0, a maintenance release that includes 2 new features and 2 bug fixes. This pre-release is backward-compatible with 4.3.0.

Add property file-based initialization

It's now possible to use a property file to configure the ConnectionFactory (e.g. host, username, password, etc).

GitHub issue: #324

Add Java 9 module name

The Automatic-Module-Name: com.rabbitmq.client entry has been added to the JAR manifest, for interoperability with JDK 9 module system.

GitHub issue: #320

Get rid of read retry in NIO

The NIO mode used to use retries on network reading to make sure the outstanding frame would be completed in the current loop iteration. It now handle partial frames and moves on if a frame cannot be completed immediately. This behaviour is more consistent with NIO usage.

GitHub issue: #319

Load client version in a more reliable way

This could affect classpath-sensitive environments like OSGi.

GitHub issue: #334

4.4.0.RC1

Changes between 4.3.0 and 4.4.0.RC1

This is a release candidate for 4.4.0, a maintenance release that includes 2 new features and bug fix. This pre-release is backward-compatible with 4.3.0.

Add property file-based initialization

It's now possible to use a property file to configure the ConnectionFactory (e.g. host, username, password, etc).

GitHub issue: #324

Add Java 9 module name

The Automatic-Module-Name: com.rabbitmq.client entry has been added to the JAR manifest, for interoperability with JDK 9 module system.

GitHub issue: #320

Get rid of read retry in NIO

The NIO mode used to use retries on network reading to make sure the outstanding frame would be completed in the current loop iteration. It now handle partial frames and moves on if a frame cannot be completed immediately. This behaviour is more consistent with NIO usage.

GitHub issue: #319

4.3.0

Changes between 4.2.2 and 4.3.0

This maintenance release includes 2 new features and a bug fix. It's backward compatible with 4.2.x. Users of the 4.x.x and 3.6.x series are encouraged to use this release.

Support Micrometer

The Java Client supports Micrometer through its MicrometerMetricsCollector implementation of MetricsCollector. Micrometer is an instrumentation facade, which supports popular metrics backends (Atlas, Graphite, Ganglia, Datadog, JMX, etc). Note Micrometer requires Java 8 or more. The Java Client 4.3.x still supports Java 6, but Micrometer support isn't usable on Java 6 and Java 7.

GitHub issue: #313

Make auto-recovery retry interval calculation pluggable

The RecoveryDelayHandler interface has been introduced to calculate the retry interval between each connection recovery attempt. The default strategy is still the same: a constant interval (5 seconds by default). The ExponentialBackoffDelayHandler implementation can be used to have an exponential retry interval.

Thanks to @vikinghawk for this contribution.

GitHub issue: #308

Handle several buffer underflow results in SslEngineByteBufferInputStream

Thanks to @dimas for this fix.

GitHub issue: #317

4.3.0.RC2

Changes between 4.2.2 and 4.3.0.RC2

This is a release candidate for 4.3.0, a maintenance release that includes 2 new features and bug fix. This release is backward-compatible with 4.2.2.

Support Micrometer

The Java Client supports Micrometer through its MicrometerMetricsCollector implementation of MetricsCollector. Micrometer is an instrumentation facade, which supports popular metrics backends (Atlas, Graphite, Ganglia, Datadog, JMX, etc). Note Micrometer requires Java 8 or more. The Java Client 4.3.x still supports Java 6, but Micrometer support isn't usable on Java 6 and Java 7.

GitHub issue: #313

Make auto-recovery retry interval calculation pluggable

The RecoveryDelayHandler interface has been introduced to calculate the retry interval between each connection recovery attempt. The default strategy is still the same: a constant interval (5 seconds by default). The ExponentialBackoffDelayHandler implementation can be used to have an exponential retry interval.

Thanks to @vikinghawk for this contribution.

GitHub issue: #308

Handle several buffer underflow results in SslEngineByteBufferInputStream

Thanks to @dimas for this fix.

GitHub issue: #317

4.3.0.RC1

Changes between 4.2.2 and 4.3.0.RC1

This is a release candidate for 4.3.0.RC1, a maintenance release that includes 2 new features. This release is backward-compatible with 4.2.2.

Support Micrometer

The Java Client supports Micrometer through its MicrometerMetricsCollector implementation of MetricsCollector. Micrometer is an instrumentation facade, which supports popular metrics backends (Atlas, Graphite, Ganglia, Datadog, JMX, etc). Note Micrometer requires Java 8 or more. The Java Client 4.3.x still supports Java 6, but Micrometer support isn't usable on Java 6 and Java 7.

GitHub issue: #313

Make auto-recovery retry interval calculation pluggable

The RecoveryDelayHandler interface has been introduced to calculate the retry interval between each connection recovery attempt. The default strategy is still the same: a constant interval (5 seconds by default). The ExponentialBackoffDelayHandler implementation can be used to have an exponential retry interval.

Thanks to @vikinghawk for this contribution.

GitHub issue: #308