4.8.0.RC1

This is a pre-release for 4.8.0, a maintenance release with new features. It is compatible with 4.7.x. All users of the 4.x.x and 3.6.x series are encouraged to test this version.

Changes between 4.7.0 and 4.8.0.RC1

Add filter to skip some entities on topology recovery

GitHub issue: #383

Add optional retry logic to topology recovery

GitHub issue: #387

Address parser is incapable of handling IPv6 address literals

GitHub issue: #385

Improve JSON RPC support by using Jackson

GitHub issue: #378

Add equals and hashCode to generated classes

GitHub issue: #377

Add dedicated executor to close connections in NIO mode

GitHub issue: #380

5.4.0.M1

This is a pre-release for 5.4.0, a maintenance release with new features and a bug fix. It is compatible with 5.3.x. All users of the 5.x.x series are encouraged to test this version.

Changes between 5.3.0 and 5.4.0.M1

Add filter to skip some entities on topology recovery

GitHub issue: #383

Add optional retry logic to topology recovery

GitHub issue: #387

Address parser is incapable of handling IPv6 address literals

GitHub issue: #385

Add option for connection recovery triggering

GitHub issue: #379

Continuations (requests) are not discarded on timeouts

GitHub issue: #375

4.8.0.M1

This is a pre-release for 4.8.0, a maintenance release with new features. It is compatible with 4.7.x. All users of the 4.x.x and 3.6.x series are encouraged to test this version.

Changes between 4.7.0 and 4.8.0.M1

Add filter to skip some entities on topology recovery

GitHub issue: #383

Add optional retry logic to topology recovery

GitHub issue: #387

Address parser is incapable of handling IPv6 address literals

GitHub issue: #385

5.3.0

This is a maintenance release with a new feature, a usability improvement, and a bug fix. It is compatible with 5.2.x. All users of the 5.x.x series are encouraged to use this version. Users of previous versions should check the 5.0.0 changelog for breaking changes.

Changes between 5.2.0 and 5.3.0

Multi-threaded topology recovery

Automatic topology recovery can now be performed with an ExecutorService provided with ConnectionFactory#setTopologyRecoveryExecutor. This can speed up topology recovery for connections that have lots of queues and bindings. Early tests showed multi-threaded topology recovery can be 5 times faster than single-threaded topology recovery. Note single-threaded topology recovery is still the default.

Thanks to @vikinghawk for this contribution.

GitHub PR: #370

Reduce default channel max to 2047

Max number of channels has been reduced from unlimited to 2048 as of RabbitMQ 3.7.5, to avoid leaking-channel applications starving broker resources. This client-side change is a safety measure for clients that would upgrade the server later.

GitHub issue: #366

Use default client properties when reading from properties file

GitHub issue: #368

4.7.0

This is a maintenance release with a new feature, a usability improvement, and a bug fix. It is compatible with 4.6.x. All users of the 4.x.x and 3.6.x series are encouraged to use this version.

Changes between 4.6.0 and 4.7.0

Multi-threaded topology recovery

Automatic topology recovery can now be performed with an ExecutorService provided with ConnectionFactory#setTopologyRecoveryExecutor. This can speed up topology recovery for connections that have lots of queues and bindings. Early tests showed multi-threaded topology recovery can be 5 times faster than single-threaded topology recovery. Note single-threaded topology recovery is still the default.

Thanks to @vikinghawk for this contribution.

GitHub PR: #370

Reduce default channel max to 2047

Max number of channels has been reduced from unlimited to 2048 as of RabbitMQ 3.7.5, to avoid leaking-channel applications starving broker resources. This client-side change is a safety measure for clients that would upgrade the server later.

GitHub issue: #366

Use default client properties when reading from properties file

GitHub issue: #368

6.0.0.M1

This is the first milestone release for 6.0.0. It introduces new metrics on published messages. This pre-release introduces also a breaking change which impacts users implementing the MetricsCollector interface in their applications. Users of the 5.x.x series are encouraged to test this version.

Changes between 5.x.x and 6.0.0.M1

Metrics for confirmed and unsuccessful outgoing publishes

The client now collects metrics on confirmed, failed, nacked, and unroutable outgoing messages. This change implies a change in the MetricsCollector interface. This is a breaking change for anyone implementing this interface in their application (which is unlikely to be).

Thanks to @slayful for this contribution.

GitHub PR: #354

5.3.0.RC1

This is a pre-release for 5.3.0, a maintenance release with a new feature, a bug fix, and usability improvements. It is compatible with 5.2.x. All users of the 5.x.x series are encouraged to test this version.

Changes between 5.2.0 and 5.3.0.RC1

Multi-threaded topology recovery

Automatic topology recovery can now be performed with an ExecutorService provided with ConnectionFactory#setTopologyRecoveryExecutor. This can speed up topology recovery for connections that have lots of queues and bindings. Early tests showed multi-threaded topology recovery can be 5 times faster than single-threaded topology recovery. Note single-threaded topology recovery is still the default.

Thanks to @vikinghawk for this contribution.

GitHub PR: #370

Throw an exception instead of trying to transmit a header frame that exceeds max frame size

Thanks to @ibolotin for this contribution.

GitHub issue: #362

Reduce default channel max to 2047

Max number of channels has been reduced from unlimited to 2048 as of RabbitMQ 3.7.5, to avoid leaking-channel applications starving broker resources. This client-side change is a safety measure for clients that would upgrade the server later.

GitHub issue: #366

Use default client properties when reading from properties file

GitHub issue: #368

4.7.0.RC1

This is a pre-release for 4.7.0, a maintenance release with a new feature, a usability improvement, and a bug fix. It is compatible with 4.6.x. All users of the 4.x.x and 3.6.x series are encouraged to test this version.

Changes between 4.6.0 and 4.7.0.RC1

Multi-threaded topology recovery

Automatic topology recovery can now be performed with an ExecutorService provided with ConnectionFactory#setTopologyRecoveryExecutor. This can speed up topology recovery for connections that have lots of queues and bindings. Early tests showed multi-threaded topology recovery can be 5 times faster than single-threaded topology recovery. Note single-threaded topology recovery is still the default.

Thanks to @vikinghawk for this contribution.

GitHub PR: #370

Reduce default channel max to 2047

Max number of channels has been reduced from unlimited to 2048 as of RabbitMQ 3.7.5, to avoid leaking-channel applications starving broker resources. This client-side change is a safety measure for clients that would upgrade the server later.

GitHub issue: #366

Use default client properties when reading from properties file

GitHub issue: #368

4.6.0

This is a maintenance release with dependency upgrades only. It is compatible with 4.5.x. All users of the 4.x.x and 3.6.x series are encouraged use this version.

Changes between 4.5.0 and 4.6.0

Upgrade to Micrometer 1.0.2

MicrometerMetricsCollector was using API from Micrometer 1.0.0.rc6 and those API were removed in Micrometer 1.0.0 GA. MicrometerMetricsCollector has been fixed to work against Micrometer 1.0.x.

GitHub issues: #351, #353

Upgrade dependencies

Upgrade to SLF4J 1.7.25 (mandatory dependency) and to Dropwizard Metrics 3.2.6 (optional dependency). This shouldn't impact applications whatsoever.

GitHub commit: eed963c

4.6.0.RC1

This is a pre-release for 4.6.0, a maintenance release with dependency upgrades only. It is compatible with 4.5.x. All users of the 4.x.x and 3.6.x series are encouraged to test this version.

Changes between 4.5.0 and 4.6.0.RC1

Upgrade to Micrometer 1.0.2

MicrometerMetricsCollector was using API from Micrometer 1.0.0.rc6 and those API were removed in Micrometer 1.0.0 GA. MicrometerMetricsCollector has been fixed to work against Micrometer 1.0.x.

GitHub issues: #351, #353

Upgrade dependencies

Upgrade to SLF4J 1.7.25 (mandatory dependency) and to Dropwizard Metrics 3.2.6 (optional dependency). This shouldn't impact applications whatsoever.

GitHub commit: eed963c