Release Notes for AMQ Interconnect 1.10

Red Hat AMQ 2021.q1

Release Notes for AMQ Interconnect


These release notes contain the latest information about new features, enhancements, fixes, and issues contained in the AMQ Interconnect 1.10 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 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 OpenShift Container Platform versions 4.6, 4.7 or 4.8.

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 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 6. Fixed issues

  • 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 7. Known issues

  • ENTMQIC-1980 - Symbolic ports in HTTP listeners do not work

    When configuring a listener in the router with the http option enabled (for console or WebSocket access), the port attribute 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 2021-09-29 11:07:22 UTC

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 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.