AMQ Interconnect Operator now available for deploying AMQ Interconnect in OpenShift 4.1. The AMQ Interconnect Operator offers flexible deployment plans for interior and edge router network deployments, connectivity configuration defaults, and automated security certificate management.

For more information, see Deploying AMQ Interconnect on OpenShift Container Platform.

ENTMQIC-2219 - Console access to the force-close a connection feature

In the AMQ Interconnect web console, you can now close AMQP client connections.

ENTMQIC-61 - Memory pools are never returned to heap

Several heavily used data objects (deliveries, messages, links, buffers, etc.) are managed by AMQ Interconnect in pools for efficient allocation. In AMQ Interconnect 1.1, 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.

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
    ...
}