4.5.0.RC3

Changes between 4.4.2 and 4.5.0.RC2

This is a release candidate for 4.5.0, a maintenance release that includes new features and bug fixes. It also fixes a bug introduced in 4.5.0.RC2 whereby non-recoverable connections could swallow IO exceptions. This pre-release is backward-compatible with 4.4.0.

Introduce CredentialsProvider interface for authentication

This can be used to provide different credentials between re-connection.

Thanks to @spatula75 for this contribution.

GitHub PR: #350

Add excludeQueueFromRecovery method

This adds a public method to AutorecoveringConnection to allow for removal of a queue from recorded queues (and its related bindings) without having to call Channel#queueDelete.

Thanks to @vikinghawk for this contribution.

GitHub PR: #346

Trigger recovery if a socket write fails

Detecting connection failure on reading can take a lot of time (even forever if the reading thread is stuck), so connection recovery can now be triggered when a write operation fails. This can make the client more reactive to detect TCP connection failure.

GitHub issue: #341

Add RpcClient doCall/responseCall/primitiveCall overloads which include timeout

Thanks to @AndreasPresthammer for this contribution.

GitHub PR: #338

Fix a potential race condition between channel recovery and acknowledgement offset

During recovery, when attempting to acknowledge a delivery the channel could be closed with
reply-code=406, reply-text=PRECONDITION_FAILED - unknown delivery tag 0, class-id=60, method-id=80) and messages would stop being delivered.

Thanks to @vikinghawk for this contribution.

GitHub PR: #343

4.5.0.RC2

Changes between 4.4.2 and 4.5.0.RC2

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

Introduce CredentialsProvider interface for authentication

This can be used to provide different credentials between re-connection.

Thanks to @spatula75 for this contribution.

GitHub PR: #350

Add excludeQueueFromRecovery method

This adds a public method to AutorecoveringConnection to allow for removal of a queue from recorded queues (and its related bindings) without having to call Channel#queueDelete.

Thanks to @vikinghawk for this contribution.

GitHub PR: #346

Trigger recovery if a socket write fails

Detecting connection failure on reading can take a lot of time (even forever if the reading thread is stuck), so connection recovery can now be triggered when a write operation fails. This can make the client more reactive to detect TCP connection failure.

GitHub issue: #341

Add RpcClient doCall/responseCall/primitiveCall overloads which include timeout

Thanks to @AndreasPresthammer for this contribution.

GitHub PR: #338

Fix a potential race condition between channel recovery and acknowledgement offset

During recovery, when attempting to acknowledge a delivery the channel could be closed with
reply-code=406, reply-text=PRECONDITION_FAILED - unknown delivery tag 0, class-id=60, method-id=80) and messages would stop being delivered.

Thanks to @vikinghawk for this contribution.

GitHub PR: #343

4.5.0.RC1

Changes between 4.4.2 and 4.5.0.RC1

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

Add excludeQueueFromRecovery method

This adds a public method to AutorecoveringConnection to allow for removal of a queue from recorded queues (and its related bindings) without having to call Channel#queueDelete.

Thanks to @vikinghawk for this contribution.

GitHub PR: #346

Add RpcClient doCall/responseCall/primitiveCall overloads which include timeout

Thanks to @AndreasPresthammer for this contribution.

GitHub PR: #338

Fix a potential race condition between channel recovery and acknowledgement offset

During recovery, when attempting to acknowledge a delivery the channel could be closed with
reply-code=406, reply-text=PRECONDITION_FAILED - unknown delivery tag 0, class-id=60, method-id=80) and messages would stop being delivered.

Thanks to @vikinghawk for this contribution.

GitHub PR: #343

5.1.2

Changes between 5.1.1 and 5.1.2

This patch release improves Micrometer support and fixes a bug that can occur when using metrics in combination with automatic recovery. All users of the 5.x.x series are encouraged to upgrade to this release.

Support tags in Micrometer metrics collector

GitHub issue: #342

Upgrade Micrometer to 1.0.0-rc.6

GitHub issue: #340

Fix metrics for acked/nacked/rejected messages after automatic recovery has kicked in

The metrics are correct and delivery tags no longer leak in the metrics implementation.

GitHub issue: #339

4.4.2

Changes between 4.4.1 and 4.4.2

This patch release improves Micrometer support and fixes a bug that can occur when using metrics in combination with automatic recovery. All users of the 4.x.x series are encouraged to upgrade to this release.

Support tags in Micrometer metrics collector

GitHub issue: #342

Upgrade Micrometer to 1.0.0-rc.6

GitHub issue: #340

Fix metrics for acked/nacked/rejected messages after automatic recovery has kicked in

The metrics are correct and delivery tags no longer leak in the metrics implementation.

GitHub issue: #339

5.1.2.RC2

Changes between 5.1.1 and 5.1.2.RC2

This is a pre-release for 5.1.2, a patch pre-release that fixes a bug that can occur when using metrics in combination with automatic recovery. All users of the 5.x.x series are encouraged to test this pre-release.

Fix metrics for acked/nacked/rejected messages after automatic recovery has kicked in

The metrics are correct and delivery tags no longer leak in the metrics implementation.

GitHub issue: #339

Support tags in Micrometer metrics collector

GitHub issue: #342

Upgrade Micrometer to 1.0.0-rc.6

GitHub issue: #340

4.4.2.RC2

Changes between 4.4.1 and 4.4.2.RC2

This is a pre-release for 4.4.2, a patch pre-release that fixes a bug that can occur when using metrics in combination with automatic recovery and improves Micrometer support. All users of the 4.x.x series are encouraged to test this pre-release.

Fix metrics for acked/nacked/rejected messages after automatic recovery has kicked in

The metrics are correct and delivery tags no longer leak in the metrics implementation.

GitHub issue: #339

Support tags in Micrometer metrics collector

GitHub issue: #342

Upgrade Micrometer to 1.0.0-rc.6

GitHub issue: #340

5.1.2.RC1

Changes between 5.1.1 and 5.1.2.RC1

This is a pre-release for 5.1.2, a patch pre-release that fixes a bug that can occur when using metrics in combination with automatic recovery. All users of the 5.x.x series are encouraged to test this pre-release.

Fix metrics for acked/nacked/rejected messages after automatic recovery has kicked in

The metrics are correct and delivery tags no longer leak in the metrics implementation.

GitHub issue: #339

4.4.2.RC1

Changes between 4.4.1 and 4.4.2.RC1

This is a pre-release for 4.4.2, a patch pre-release that fixes a bug that can occur when using metrics in combination with automatic recovery. All users of the 4.x.x series are encouraged to test this pre-release.

Fix metrics for acked/nacked/rejected messages after automatic recovery has kicked in

The metrics are correct and delivery tags no longer leak in the metrics implementation.

GitHub issue: #339

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