Release Notes for AMQ Interconnect 1.9

Red Hat AMQ 2020.Q4

Release Notes for AMQ Interconnect

Abstract

These release notes contain the latest information about new features, enhancements, fixes, and issues contained in the AMQ Interconnect 1.9 release.

Chapter 1. Enhancements

  • ENTMQIC-2448 - Allow defining address prefix shared by different multitenant listeners

    With this release a multitenant prefix specified by a vhost policy can be shared among several hostnames with a pattern specified in the aliases parameter as described in Creating vhost policies.

Chapter 2. Fixed issues

  • CVE-2020-7656 - jquery: allows XSS via the load method [amq-ic-1]

    The issue has been resolved by updating the jQuery dependency.

  • CVE-2020-11022 - jquery: Cross-site scripting due to improper injQuery.htmlPrefilter method [amq-ic-1]

    The issue has been resolved by updating the jQuery dependency.

  • CVE-2020-11023 - jquery: passing HTML containing <option> elements to manipulation methods could result in untrusted code execution [amq-ic-1]

    The issue has been resolved by updating the jQuery dependency.

  • ENTMQIC-2446 - Router crash with epoll error EPOLL_CTL_DEL

    Previously, the router could crash due to a race condition.

    The issue has been resolved.

  • ENTMQIC-2485 - The VhostNamePatterns does not work in OCP env

    Previously, using # in the hostname of a vhost policy did not set the policy correctly.

    The issue has been fixed.

  • ENTMQIC-2481 - Unable to delete listener with http enabled

    Previously, if you created a listener with http set to true you could not later delete that listener.

    The issue has been fixed.

  • ENTMQIC-2460 - Adding new config address, autolinks and link routes become slower as more get added

    Previously, if you created many addresses the creation of more addresses becomes slow.

    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-10-08 11:22:32 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 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.