이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Release Notes for AMQ Interconnect 1.10
Release Notes for AMQ Interconnect
Abstract
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Long Term Support for AMQ Interconnect 1.10
AMQ Interconnect 1.10 has been designated as a Long Term Support (LTS) release version. Bug fixes and security advisories will be made available for AMQ Interconnect 1.10 in a series of micro releases (1.10.1, 1.10.2, 1.10.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 Interconnect 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 Interconnect 1.10.0 GA.
AMQ Interconnect 2 will not support OpenShift Container Platform 3.11. To continue using OpenShift Container Platform 3.11, Red Hat recommends using this LTS release.
Chapter 2. End of Red Hat Enterprise Linux 6 support
As of version 1.10, AMQ Interconnect 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.
Chapter 3. OpenShift Container Platform versions
AMQ Interconnect 1.10 is supported on the OpenShift Container Platform versions listed in the Supported Configurations page.
With OpenShift Container Platform 4.9, deprecated APIs are removed from OpenShift, requiring the following actions before upgrading:
- You must update to AMQ Interconnect 1.10.2 before you can upgrade to OpenShift Container Platform version 4.9. If you attempt to upgrade to OpenShift Container Platform version 4.9 while an earlier version of the AMQ Interconnect Operator is installed in the cluster, an error is displayed.
- The Red Hat Integration - AMQ Certificate Manager Operator is not supported on OpenShift Container Platform version 4.9 or later. If you attempt to upgrade to OpenShift Container Platform version 4.9 while the AMQ Certificate Manager Operator is installed in the cluster, an error is displayed. Migrating from the Red Hat Integration - AMQ Certificate Manager Operator is described in Deploying AMQ Interconnect on OpenShift.
Chapter 4. New and changed features
AMQ Interconnect 1.10 includes the following changes:
- Red Hat Enterprise Linux 6 is no longer supported with this release.
Chapter 5. Using the Operator on restricted networks
With 1.10.4, AMQ Interconnect is supported on restricted networks. See Deploying AMQ Interconnect on OpenShift for instructions on deploying AMQ Interconnect in a restricted environment.
Chapter 6. Using qdstat or qdmanage over SSL/TLS
With the Interconnect 1.10.1 release, certificates are verified using the system Certificate Authority (CA) when using qdstat or qdmanage over SSL/TLS and the --ssl-trustfile is not specified. Typically, the system CA is not used to issue these certificates and the connection fails.
If you use qdstat or qdmanage to connect to a router over SSL/TLS, specify the CA file to authenticate that router to avoid connection issues. For example:
$ qdstat --ssl-trustfile <pem-database-file>
Chapter 7. Fixed issues
ENTMQIC-2752 - Some details missing on dispositions forwarded by router on transacted sessions
Previously, as messages moved from a client through a router to a broker in a transacted session, the disposition from the broker was not forwarded from the router back to the client.
This issue has been resolved.
ENTMQIC-2624 - Provide example yaml files for installation of operator and container image
Previously, if you wanted to use the AMQ Interconnect Operator, you had to provision it using the OperatorHub.
The release includes files and instructions to provision the operator from the command-line.
ENTMQIC-2427 - In qpid-dispatch-console the addresses page is not showing the ingress and egress counts properly
Previously, the AMQ Management Console might incorrectly display 0 for delivery attribute values associated with mobile addresses.
This issue has been resolved.
Chapter 8. Known issues
ENTMQIC-1980 - Symbolic ports in HTTP listeners do not work
When configuring a listener in the router with the
httpoption enabled (for console or WebSocket access), theportattribute must be expressed numerically. Symbolic port names do not work with HTTP listeners.If a listener is configured as:
listener { ... port: amqp http: yes ... }It should be changed to:
listener { ... port: 5672 http: yes ... }
Revised on 2022-08-19 13:58:16 UTC
