-
Language:
English
-
Language:
English
Release Notes for AMQ Interconnect 1.8
Release Notes for AMQ Interconnect
Abstract
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 ofmaxMessageSize
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), 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-06-16 12:28:18 UTC