Menu Close
Settings Close

Language and Page Formatting Options

Red Hat Training

A Red Hat training course is available for Red Hat AMQ

AMQ Interconnect 1.0 Release Notes

Red Hat JBoss AMQ 7.0

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

Chapter 1. Features

AMQ Interconnect 1.0 represents the initial offering of this component as part of a complete messaging solution. Deploying an interconnect router (or network of routers) provides the following benefits over using brokers alone:

Operating modes
The interconnect component can operate in stand-alone mode or interior mode.
Brokerless messaging
Direct, brokerless messaging when broker queueing is not needed. This feature is useful for request-response/RPC patterns.
Anycast or Multicast
Direct delivery can be configured as multicast (all subscribers receive a copy of each produced message) or anycast (one subscriber receives a copy of each produced message).
Inexpensive HA and resiliency
High availability and resiliency for the network does not require high-cost clustering; it is achieved through redundant topologies much like one would use in deploying an IP network.
Scale up queues and topics
A messaging system including interconnect can offer a greater number of queues and topics than can be offered by a single broker or a cluster of brokers.
Queue/topic distribution
A single queue or topic can be distributed across multiple brokers to provide increased user scale and throughput.
Access to a broker can be secured, hardened, and limited. In addition, the broker does not need to be deployed in a client-facing DMZ (De-Militarized Zone in front of a firewall).
Connections between clients and a broker or a broker and another broker can be secured by using SSLTLS (Secure Socket Layer Top Level Specification) or SASL (Simple Authentication and Security Layer) at the interconnect level to encrypt the connections.
Brokers can be added and removed to handle changes in load or to accommodate broker maintenance.
Queues, topics, and destinations can be partitioned by user/application/account such that multiple users can use the same messaging infrastructure without interfering with each other.

Refer to the Apache QPid Dispatch Router project for additional information:

Chapter 2. Enhancements

  • ENTMQIC-1886 - Remove dependency on python-websockify websocket proxy

    Previous releases of the product used python-websockify to allow a proxy connection between the qdrouterd demon and a user’s web browser, necessary to access the HawtIO console

    The distribution now contains the libwebsockets package instead of python-websockify to establish this connection.

Chapter 3. Resolved Issues

  • ENTMQIC-1014 - CLI tools fail with no useful error in some SASL configurations

    By default, even with authenticatePeer: no, previous versions of the router were offering all available SASL mechanisms to clients (unless saslMechanisms was set explicitly) This meant that if GSS mechanisms were enabled on the host for other purposes, but not configured for the router, they would be preferred over the less secure ANONYMOUS mechanism and fail. In the current release, only ANONYMOUS is offered when setting authenticatePeer: no and any client can connect anonymously.

Chapter 4. Known Issues

  • ENTMQIC-1966 - warning: %postun(qpid-dispatch-router-0.8.0-9.el6.i686) scriptlet failed, exit status 2

    If you encounter an error warning: %postun(qpid-dispatch-router-0.8.0-9.el6.i686) scriptlet failed, exit status 2 after installing AMQ Interconnect 1.0.1, check the service qdrouterd status and restart the service if it is running, as shown in the following example:

    # service qdrouterd status
    qdrouterd (pid 3996) is running...
    # service qdrouterd restart
    Shutting down qdrouterd services: [ OK ]
    Starting qdrouterd services: [ OK ]
    # service qdrouterd status
    qdrouterd (pid 4384) is running...
  • ENTMQIC-61 - Memory pools are never returned to heap

    Several heavily used data objects (deliveries, messages, links, buffers, etc.) are managed by Qpid Dispatch Router in pools for efficient allocation. In AMQ Interconnect 1.0, 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 and a solution will be included in a future version of the Router.

Revised on 2017-11-22 09:42:38 EST

Legal Notice

Copyright © 2017 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, 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 Software Collections 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.