Release Notes for AMQ Online 1.7 on OpenShift
Release Notes for AMQ Online 1.7 on OpenShift Container Platform
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 Online 1.7
AMQ Online 1.7 has been designated as a Long Term Support (LTS) release version. Bug fixes and security advisories will be made available for AMQ Online 1.7 in a series of micro releases (1.7.1, 1.7.2, 1.7.3, and so on) until the product’s end of life. Note the following important points about the LTS release stream:
- The LTS release stream provides only bug fixes and security advisories. 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 from the time of the AMQ Online 1.7.0 GA until the product’s end of life.
Chapter 2. AMQ Online component versions
AMQ Online 1.7 on OpenShift Container Platform is based on AMQ Broker 7.8 and AMQ Interconnect 1.10.
Chapter 3. Enhancements
3.1. Configuring the maximum size of AMQP message transfers allowed for a router
router.policy.maxMessageSize field to the standard infrastructure configuration. This field specifies the maximum size in bytes of AMQP message transfers allowed for a router. For more information, see Standard infrastructure configuration fields.
3.2. Enabling global dead letter address
globalDLQ field to the standard infrastructure configuration. If set to
true, the system establishes a fallback global dead letter address named
!!GLOBAL_DLQ. For more information, see Standard infrastructure configuration fields.
Chapter 4. Fixed issues
ENTMQMAAS-2632 - Agent utilizes unexpectedly high CPU/memory when a large number of connections/addresses are defined
ENTMQMAAS-2640 - Idle timeout of outbound broker connection may not trigger reconnection
Previously, when the internal AMQ Online broker plug-in detected an idle timeout of the outbound broker connection, it was not always able to reconnect to the router. This issue has been resolved.
ENTMQMAAS-2641 - Address/connection stats collections may erroneously run concurrently leading to excessive memory use/OOMs
Previously, for deployments with a large number of connections and addresses, the statistics collections in the agent could exceed the statistics collection period, which caused the statistics collection cycle to begin even though the previous one was still in progress. This led to memory issues. This issue has been resolved.
ENTMQMAAS-2646 - Missing autolinks following a 1.5.3 to 1.5.4 upgrade
Previously, if you upgraded from AMQ Online 1.5.3 to 1.5.4 and had an existing standard address space defined with a queue address type, those addresses reported missing autolinks. This issue is related to ENTMQMAAS-2657. These issues have been resolved.
ENTMQMAAS-2664 - Monitoring does not work on OpenShift >= 4.7
In OpenShift Container Platform 4.6 and later, user-workload monitoring changed from Technology Preview to General Availability, which changed how to enable user-workload monitoring to monitor AMQ Online. This issue has been resolved. For more information, see Enabling monitoring for user-defined projects.
ENTMQMAAS-2668 - Connections slow to appear or update in the Console
Previously, new connections or updates to the metrics of existing connections were slow to appear on the Red Hat AMQ Console for deployments with a large number of connections. This issue has been resolved.
Chapter 5. Known issues
ENTMQMAAS-1281 - Resources not deleted when uninstalling AMQ Online using OLM on OpenShift Container Platform 4.x
Workaround: For the workaround about how to remove all resources when uninstalling AMQ Online using the Operator Lifecycle Manager (OLM), see Removing remaining resources after uninstalling AMQ Online using the Operator Lifecycle Manager.
ENTMQMAAS-1799 - Possible to define duplicate addresses using router pattern-matching syntax
When defining addresses in a standard address space instance, be aware that the following restrictions affect the composition of the
spec.addressfield in the
The router specifies both period (.) and forward slash (/) characters as address separator characters and that both characters are equivalent. In addition, the router infers a leading address separator character even if it is not explicitly included.
Since AMQ Online does not encode these rules, care must be taken to avoid defining addresses that collide on the router network.
Workaround: One way to avoid this collision is to follow these guidelines for defining addresses:
- Use either a period or a forward slash in the addresses, but do not use both.
- Do not begin addresses with an address separator character.
For more information about address pattern matching on the router, see the Red Hat AMQ Interconnect documentation, Address pattern matching.