AMQ Interconnect 1.5 Release Notes

Red Hat AMQ 7.4

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

Chapter 1. Features

AMQ Interconnect 1.5 provides the following new features:

  • AMQ Interconnect Operator now available for deploying AMQ Interconnect in OpenShift 4.1. The AMQ Interconnect Operator offers flexible deployment plans for interior and edge router network deployments, connectivity configuration defaults, and automated security certificate management.

    For more information, see Deploying AMQ Interconnect on OpenShift Container Platform.

  • Fallback destinations added. For an address, you can now redirect delayed or undeliverable messages to a fallback destination. The fallback destination stores the messages until a consumer reconnects and becomes reachable.

Chapter 2. Enhancements

  • ENTMQIC-2219 - Console access to the force-close a connection feature

    In the AMQ Interconnect web console, you can now close AMQP client connections.

Chapter 3. Known issues

  • ENTMQIC-61 - Memory pools are never returned to heap

    Several heavily used data objects (deliveries, messages, links, buffers, etc.) are managed by AMQ Interconnect in pools for efficient allocation. In AMQ Interconnect 1.1, objects in these pools are not returned to the heap at any time. This means that the memory used in large bursts of activity will not be freed, but will remain available for use thereafter.

    This might be observed as an increase in memory usage that does not decrease after a burst of activity is completed. Subsequent bursts of activity will use the same memory that was used previously.

    Methods of returning large amounts of pooled objects back to the heap are being developed.

  • 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 2019-07-19 21:43:56 UTC

Legal Notice

Copyright © 2019 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.