Chapter 4. Known Issues

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-1979 - Kerberos authentication problem with amq-jms client

Kerberos (GSSAPI) authentication between the AMQ JMS client and the AMQ Interconnect router does not work and is not supported in this release.

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

ENTMQIC-1985 - Management agent misreports the SSL/TLS version

When using SSL/TLS in a connection, the management agent reports the protocol version to be TLSv1/SSLv3 when the protocol actually being used on the wire is TLSv1.2.

This is an issue in the underlying qpid-proton library and is fixed in qpid-proton 0.20.