-
Language:
English
-
Language:
English
Release Notes for AMQ Interconnect 1.9
Release Notes for AMQ Interconnect
Abstract
Chapter 1. Enhancements
ENTMQIC-2455 - Allow AMQP open properties to be supplemented from connector configuration
With this release you can now add metadata when connecting routers, as described in Adding metadata to connections.
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 thehostname
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 totrue
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), theport
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