1.10.0

Changes between 1.9.0 and 1.10.0

This is a maintenance release that includes new features, bug fixes, and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.9.0. All users of the 1.x.x series are encouraged to use this version.

Add flag to throw exception on consumer startup failure

GitHub issue: #53

Throw exception only for queues when selector is not null

GitHub issue: #52

Add ConnectionFactory post processor

GitHub issue: #57

Add option to enable hostname verification

GitHub issue: #55

Support URIs in RMQConnectionFactory

GitHub issue: #50

Support for metrics collection

GitHub issue: #49

Upgrade to Java client 4.8.1

GitHub issue: #54

1.10.0.RC1

Changes between 1.9.0 and 1.10.0.RC1

This is a release candidate for 1.10.0, a maintenance release that includes new features, bug fixes, and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.9.0.

Add flag to throw exception on consumer startup failure

GitHub issue: #53

Throw exception only for queues when selector is not null

GitHub issue: #52

Add ConnectionFactory post processor

GitHub issue: #57

Add option to enable hostname verification

GitHub issue: #55

Support URIs in RMQConnectionFactory

GitHub issue: #50

Support for metrics collection

GitHub issue: #49

Upgrade to Java client 4.8.1

GitHub issue: #54

1.9.0

Changes between 1.8.1 and 1.9.0

This is a maintenance release that includes a new feature and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.8.1. Users of the 1.x series are encouraged to upgrade to this version.

Add callback to customise properties of outbound AMQP messages

GitHub issue: #42

Upgrade to RabbitMQ Java Client 4.6.0

The JMS Client now uses RabbitMQ Java Client 4.6.0.

GitHub issue: #44

1.9.0.RC1

Changes between 1.8.1 and 1.9.0.RC1

This is a release candidate for 1.9.0, a maintenance release that includes a new feature and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.8.1.

Add callback to customise properties of outbound AMQP messages

GitHub issue: #42

Upgrade to RabbitMQ Java Client 4.6.0

The JMS Client now uses RabbitMQ Java Client 4.6.0.

GitHub issue: #44

1.8.1

Changes between 1.8.0 and 1.8.1

This is a patch release that includes a bug fix. This release is backward-compatible with 1.7.0 and 1.8.0.

Add cleanUpServerNamedQueuesForNonDurableTopicsOnSessionClose to RMQObjectFactory

Thanks to @AlexShvedoff for this contribution.

GitHub issue: #39

1.8.0

Changes between 1.7.0 and 1.8.0

This is a maintenance release that includes a new option and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.7.0.

Add option to clean up server-named queues for non-durable topics on session closing

Those queues would be cleaned only on connection closing, now they can be closed on session closing by setting RMQConnectionFactory#cleanUpServerNamedQueuesForNonDurableTopicsOnSessionClose to true. Default is false.

Thanks to @AlexShvedoff for this contribution.

GitHub pull request: #35

Upgrade to RabbitMQ Java Client 4.3.0

The JMS Client now uses RabbitMQ Java Client 4.3.0.

GitHub issue: #37

1.8.0.RC1

Changes between 1.7.0 and 1.8.0.RC1

This is a release candidate for 1.8.0, a maintenance release that includes a new option and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.7.0.

Add option to clean up server-named queues for non-durable topics on session closing

Those queues would be cleaned only on connection closing, now they can be closed on session closing by setting RMQConnectionFactory#cleanUpServerNamedQueuesForNonDurableTopicsOnSessionClose to true. Default is false.

Thanks to @AlexShvedoff for this contribution.

GitHub pull request: #35

Upgrade to RabbitMQ Java Client 4.3.0

The JMS Client now uses RabbitMQ Java Client 4.3.0.

GitHub issue: #37

1.7.0

Changes between 1.6.0 and 1.7.0

This is a maintenance release that includes bug fixes, enhancements, and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.6.0.

Let RMQObjectFactory handle properties from a hash table

It's now possible to provide all required properties via the Hashtable environment third argument of RMQObjectFactory#getObjectInstance() method. This allows the user to create client objects on WildFly via Naming subsystem configuration.

Thanks to Rémi Bantos for this contribution.

GitHub issue: #21

Add option to take message properties into account on sending

It's now possible with the RMQConnectionFactory#preferProducerMessageProperty flag set to false to take into account the JMS Message properties (priority, delivery mode, expiration date) on sending. Note this isn't compliant with the JMS specification (the default behavior follows the JMS specification).

GitHub issue: #26

Add option to requeue message on client runtime exception

The JMS specification tells to requeue a message if the client throws a RuntimeException during delivery. The RabbitMQ JMS client wouldn't do that, it would just cancel the listener. We consider this behavior to be more natural, especially when using auto-acknowledgment mode. Nevertheless, the RMQConnectionFactory#requeueOnMessageListenerException allows to comply to the specification when set to true. The default is false (dropping the message), but this default could change in the next major release.

GitHub issue: #23

Upgrade to RabbitMQ Java Client 4.1.1

The JMS Client now uses RabbitMQ Java Client 4.1.1.

GitHub issue: #18

Don't fail when sending an empty message

GitHub issue: #24

Make compliance test suite pass again

A security fixed introduced a bug that would make the Compliance Test Suite fail. This is now fixed, the CTS passes.

GitHub issue: #16

1.7.0.RC2

Changes between 1.6.0 and 1.7.0.RC2

This is a release candidate for 1.7.0, a maintenance release that includes bug fixes, enhancements, and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.6.0.

Let RMQObjectFactory handle properties from a hash table

It's now possible to provide all required properties via the Hashtable environment third argument of RMQObjectFactory#getObjectInstance() method. This allows the user to create client objects on WildFly via Naming subsystem configuration.

Thanks to Rémi Bantos for this contribution.

GitHub issue: #21

Add option to take message properties into account on sending

It's now possible with the RMQConnectionFactory#preferProducerMessageProperty flag set to false to take into account the JMS Message properties (priority, delivery mode, expiration date) on sending. Note this isn't compliant with the JMS specification (the default behavior follows the JMS specification).

GitHub issue: #26

Add option to requeue message on client runtime exception

The JMS specification tells to requeue a message if the client throws a RuntimeException during delivery. The RabbitMQ JMS client wouldn't do that, it would just cancel the listener. We consider this behavior to be more natural, especially when using auto-acknowledgment mode. Nevertheless, the RMQConnectionFactory#requeueOnMessageListenerException allows to comply to the specification when set to true. The default is false (dropping the message), but this default could change in the next major release.

GitHub issue: #23

Upgrade to RabbitMQ Java Client 4.1.1

The JMS Client now uses RabbitMQ Java Client 4.1.1.

GitHub issue: #18

Don't fail when sending an empty message

GitHub issue: #24

Make compliance test suite pass again

A security fixed introduced a bug that would make the Compliance Test Suite fail. This is now fixed, the CTS passes.

GitHub issue: #16

1.7.0.RC1

Changes between 1.6.0 and 1.7.0.RC1

This is a release candidate for 1.7.0, a maintenance release that includes a bug fix, an enhancement, and an upgrade of the RabbitMQ Java client dependency. This release is backward-compatible with 1.6.0.

Let RMQObjectFactory handle properties from a hash table

It's now possible to provide all required properties via the Hashtable environment third argument of RMQObjectFactory#getObjectInstance() method. This allows the user to create client objects on WildFly via Naming subsystem configuration.

Thanks to Rémi Bantos for this contribution.

GitHub issue: #21

Upgrade to RabbitMQ Java Client 4.1.0

The JMS Client now uses RabbitMQ Java Client 4.1.0.

GitHub issue: #18

Make compliance test suite pass again

A security fixed introduced a bug that would make the Compliance Test Suite fail. This is now fixed, the CTS passes.

GitHub issue: #16