Chapter 3. Resolved Issues

ENTMQBR-533 - Large message support is documented, but supported only with the Core protocol

Previously, sending and receiving large messages was supported only when you use the Core protocol. The 7.1 version of AMQ Broker also supports large messages when you use the OpenWire and AMQP protocols. Note that the STOMP protocol has its own method for handling large messages, which has been supported since 7.0.

ENTMQBR-701 - Clarify reserved characters in AMQ 7

In prior releases, in was unclear which characters should not be used when creating destination names, addresses, client IDs, and other configuration elements. This information was added to the product documentation titled Using AMQ Broker under the section "Address and Queue Naming Requirements".

ENTMQBR-771 - Persistent messages sent with QPID AMQP JMS client are not reflected as durable by the broker

Previously, persistent messages sent by a AMQ JMS client were not displayed as durable when browsing messages by using the AMQ Console or JMX method call. This issue is resolved in version 7.1.

ENTMQBR-793 - JMS selectors don’t work with topic-to-queue diverts (with AMQP)

Previously, when a divert was used to route messages from a topic to a queue, no messages were consumed after a consumer attached to the target queue using a selector expression. This issue is fixed in version 7.1.

ENTMQBR-803 - Remove unsupported examples shipped with AMQ7

Previous distributions of AMQ included examples from the upstream community that are not supported by Red Hat. The unsupported examples are removed in the AMQ Broker 7.1 release.

ENTMQBR-884 - [Hawtio, Artemis panel] after connecting to hawtio "Artemis" panel is not displayed

Previously, the Artemis tab would not display in the AMQ Console when used in some environments. The only tabs displayed were Connect and Dispatch Router. This issue is resolved in the 7.1 release.