AMQ Clients 2.7 Release Notes
Release Notes for Red Hat AMQ Clients
Abstract
Chapter 1. New and changed features
1.1. AMQ C++
- The minimum requirement is now Visual Studio 2015.
1.2. AMQ Python
- AMQ Python is now supported on Windows.
- For RHEL 8 and Windows, Python 3.6 is required.
1.3. AMQ JavaScript
- The minimum requirement is now Node.js 6 for RHEL 6 and RHEL 7.
- The minimum requirement is now Node.js 10 for Windows.
1.4. AMQ .NET
- AMQ .NET now supports .NET Core 3.1.
- The minimum requirement is now .NET Core 3.1 or .NET Framework 4.7.
Chapter 2. Fixed Issues
2.1. AMQ .NET
ENTMQCL-1985 - TcpKeepAliveSettings do not work on Linux
In earlier releases of the product, developers trying to use
TcpKeepAliveSettings
in a project encountered an exception.In this release, no exception is encountered when using
TcpKeepAliveSettings
.
2.2. AMQ Python
ENTMQCL-1861 - Memory leak on Container, SSL, and SSLDomain objects
In earlier releases of the product, AMQ Python sometimes did not free memory for Container, SSL, and SSLDomain objects.
In this release, the issue is fixed.
ENTMQCL-1854 - ApplicationEvent causing memory growth
In earlier releases of the product, using the AMQ Python ApplicationEvent class caused a memory leak.
In this release, the issue is fixed.
ENTMQCL-1366 - Fix the tornado example
In earlier releases of the product, the AMQ Python tornado example, including the
client_http.py
,helloworld_tornado.py
andhelloworld_direct_tornado.py
code did not work.In this release, the issue is fixed.
Chapter 3. Important notes
3.1. AMQ C++
Unsettled interfaces
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::codec
andproton::io
namespaces and the following interfaces in theproton
namespace.-
listen_handler
-
The
on_sender_drain_start
andon_sender_drain_finish
methods onmessaging_handler
-
The
draining
andreturn_credit
methods onsender
-
The
draining
anddrain
methods onreceiver
API elements present in header files but not yet documented are considered unsettled and are subject to change.
-
Deprecated interfaces
Interfaces marked Deprecated in the API reference are scheduled for removal in a future release.
This release deprecates the following interfaces in the
proton
namespace.-
void_function0
- Use thework
class or C++11 lambdas instead. -
default_container
- Use thecontainer
class instead. -
url
andurl_error
- Use a third-party URL library instead.
-
3.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)
3.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.
3.4. Upstream versions
- AMQ C++, AMQ Python, and AMQ Ruby are now based on Qpid Proton 0.31.0.
- AMQ JavaScript is now based on Rhea 1.0.21.
- AMQ .NET is now based on AMQP.Net Lite 2.4.0.
- AMQ JMS is now based on Qpid JMS 0.51.0.
- AMQ Core Protocol JMS is now based on ActiveMQ Artemis 2.11.0.
- AMQ OpenWire JMS is now based on ActiveMQ 5.11.0.
- AMQ JMS Pool is now based on Pooled JMS 1.1.0.
- AMQ Resource Adapter is now based on AMQP 1.0 Resource Adapter 1.0.0.
- AMQ Spring Boot Starter is now based on AMQP 1.0 JMS Spring Boot 2.2.7.
- AMQ Netty OpenSSL is now based on netty-tcnative 2.0.29.Final.
Chapter 4. Important links
- Red Hat AMQ 7 Supported Configurations
- Red Hat AMQ 7 Component Details
- AMQ Clients 2.6 Release Notes
- AMQ Clients 2.5 Release Notes
- AMQ Clients 2.4 Release Notes
- AMQ Clients 2.3 Release Notes
- AMQ Clients 2.2 Release Notes
- AMQ Clients 2.1 Release Notes
- AMQ Clients 2.0 Release Notes
- AMQ Clients 1.2 Release Notes
- AMQ Clients 1.1 Release Notes
Revised on 2020-06-23 07:17:30 UTC