Release Notes for AMQ Interconnect 1.8

Red Hat AMQ 7.7

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

Chapter 1. Enhancements

  • ENTMQIC-2354 - Ability to set a maximum message size and have attempts exceeding this rejected with a clear error

    The vhost policy definition now supports a new maxMessageSize option. The value of maxMessageSize determines the maximum size in bytes of AMQP message transfers allowed for connections to the vhost.

  • ENTMQIC-2450 - Reimplement mobile-sync as a core module

    Previous releases of AMQ Interconnect supported mobile addresses, so that any user of an address may be directly connected to any router in the router network and may even move around the topology. In cases where messages are broadcast to or balanced across multiple consumers, the users of the address may be connected to multiple routers in the network.

    With this release, the support of mobile addresses is a core component to improve performance of this feature.

  • ENTMQIC-2451 - Add ability to turn on router trace logging for a specific connection

    With this release you can you can use qdmanage to enable protocol-level trace logging for a particular connection.

  • ENTMQIC-2452 - Add a "qdr" prefix to the names of our metrics

    To ensure uniqueness, all metrics are now prefixed with the string qdr.

Chapter 2. Fixed issues

  • ENTMQIC-2424 - Qpid dispatch console keeps trying to open connections when using empty username and password against a listener configured with SASL plain

    Previously, if there was an HTTP listener configured to use SASL Plain authentication, then you attempted to log into the console with both username and password fields empty, the console process would continually attempt to open new connections to the router.

    The issue has been fixed.

  • ENTMQIC-2425 - After logging in to the qpid-dispatch-console, using sasl plain authentication, the username (on the top menu) is shown as "anonymous"

    Previously, if you logged into the console using SASL Plain authentication, the correct username did not appear in the console.

    The issue has been fixed.

Chapter 3. 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 2020-06-23 07:18:47 UTC

Legal Notice

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