Release Notes for AMQ Online 1.7 on OpenShift

Red Hat AMQ 2021.Q1

Release Notes for AMQ Online 1.7 on OpenShift Container Platform

Abstract

These release notes contain the latest information about new features, enhancements, fixes, and issues contained in the AMQ Online 1.7 on OpenShift Container Platform release.

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

Added the 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

Added the 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

    Previously, deployments with a large number of connections and addresses caused unexpectedly high CPU usage. This issue has been resolved and is related to ENTMQMAAS-2641 and ENTMQMAAS-2668.

  • 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.address field in the address resource.

    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.

Legal Notice

Copyright © 2021 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.