이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 3. Important notes
3.1. End of Red Hat Enterprise Linux 6 support
As of version 2.9, AMQ Clients no longer supports Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 6 ended maintenance support on November 30th, 2020. For more information, see Red Hat Enterprise Linux Life Cycle.
3.2. Long term support
AMQ Clients 2.9 has been designated as a long term support (LTS) release version. Bug fixes and security advisories will be made available for AMQ Clients 2.9 in a series of micro releases (2.9.1, 2.9.2, 2.9.3, and so on) for a period of at least 12 months.
This means that you will be able to get recent bug fixes and security advisories for AMQ Clients without having to upgrade to a new minor release.
Note the following important points about the LTS release stream:
- The LTS release stream provides only bug fixes. No new enhancements will be added to this stream.
- To remain in a supported configuration, you must upgrade to the latest micro release in the LTS release stream.
- The LTS version will be supported for at least 12 months from the time of the AMQ Clients 2.9.0 GA.
3.3. 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::codecandproton::ionamespaces and the following interfaces in theprotonnamespace.-
listen_handler -
The
on_sender_drain_startandon_sender_drain_finishmethods onmessaging_handler -
The
drainingandreturn_creditmethods onsender -
The
draininganddrainmethods 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
protonnamespace.-
void_function0- Use theworkclass or C++11 lambdas instead. -
default_container- Use thecontainerclass instead. -
urlandurl_error- Use a third-party URL library instead.
-
3.4. 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.5. 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.6. Upstream versions
- AMQ C++, AMQ Python, and AMQ Ruby are now based on Qpid Proton 0.33.0.
- AMQ JavaScript is now based on Rhea 1.0.24.
- AMQ .NET is now based on AMQP.Net Lite 2.4.0.
- AMQ JMS is now based on Qpid JMS 0.55.0.
- AMQ Core Protocol JMS is now based on ActiveMQ Artemis 2.16.0.
- AMQ OpenWire JMS is now based on ActiveMQ 5.11.0.
- AMQ JMS Pool is now based on Pooled JMS 1.2.1.
- AMQ Resource Adapter is now based on AMQP 1.0 Resource Adapter 1.0.2.
- AMQ Spring Boot Starter is now based on AMQP 1.0 JMS Spring Boot 2.3.6.
- AMQ Netty OpenSSL is now based on netty-tcnative 2.0.34.Final.
