AMQ Clients 2.6 Release Notes
Release Notes for Red Hat AMQ Clients
Chapter 1. Features
- The clients have a new suite of examples and expanded documentation.
Chapter 2. Enhancements
2.1. AMQ JMS
ENTMQCL-1726 - Improve performance when using simulated anonymous producers
When connected to servers that do not support anonymous senders, the client now caches senders in order to improve performance.
2.2. AMQ Python
ENTMQCL-1361 - Convert strings in the API to AMQP symbols where required
The client now converts Python strings to AMQP symbols in contexts where symbols are required.
Chapter 3. Fixed issues
3.1. AMQ JMS
ENTMQCL-1835 - Consumers using a
CLIENT_ACKNOWLEDGEsession do not increment the remote delivery count after session recovery
In earlier releases of the product, consumers created with a session in
CLIENT_ACKNOWLEDGEmode did not increment the remote delivery count if the session was lost and recovered and the deliveries were not acknowledged after recovery.
In this release, the client sends delivery state updates for messages as the consumer or session is closed to ensure the delivery count is correctly updated.
3.2. AMQ Python
ENTMQCL-1364 - The client abruptly disconnects after a TCP half-close
In earlier releases of the product, a TCP half-close from a remote peer triggered an AMQP framing error. This appeared as an error even though it was a normal connection close condition.
In this release, the client correctly closes the connection without error in this case.
ENTMQCL-1578 - The client leaks transport and selectable objects
In earlier releases of the product, circular references in the client implementation caused memory use to increase over time.
In this release, the circularity of the references is broken so that memory is correctly freed.
Chapter 4. Important notes
4.1. AMQ C++
The AMQ C++ messaging API includes classes and methods that are not yet proven and can change in future releases. Be aware that use of these interfaces might require changes to your application code in the future.
These interfaces are marked Unsettled API in the API reference. They include the interfaces in the
proton::ionamespaces and the following interfaces in the
API elements present in header files but not yet documented are considered unsettled and are subject to change.
Interfaces marked Deprecated in the API reference are scheduled for removal in a future release.
This release deprecates the following interfaces in the
void_function0- Use the
workclass or C++11 lambdas instead.
default_container- Use the
url_error- Use a third-party URL library instead.
4.2. Preferred clients
In general, AMQ clients that support the AMQP 1.0 standard are preferred for new application development. However, the following exceptions apply:
- If your implementation requires distributed transactions, use the AMQ Core Protocol JMS client.
- If you require MQTT or STOMP in your domain (for IoT applications, for instance), use community-supported MQTT or STOMP clients.
The considerations above do not necessarily apply if you are already using:
- The AMQ OpenWire JMS client (the JMS implementation previously provided in A-MQ 6)
- The AMQ Core Protocol JMS client (the JMS implementation previously provided with HornetQ)
4.3. Legacy clients
Deprecation of the CMS and NMS APIs
The ActiveMQ CMS and NMS messaging APIs are deprecated in AMQ 7. It is recommended that users of the CMS API migrate to AMQ C++, and users of the NMS API migrate to AMQ .NET. The CMS and NMS APIs might have reduced functionality in AMQ 7.
Deprecation of the legacy AMQ C++ client
The legacy AMQ C++ client (the C++ client previously provided in MRG Messaging) is deprecated in AMQ 7. It is recommended that users of this API migrate to AMQ C++.
The Core API is unsupported
The Artemis Core API client is not supported. This client is distinct from the AMQ Core Protocol JMS client, which is supported.