Chapter 3. Resolved Issues
ENTMQBR-785 - Changing a queue attribute can result in lost messages
Previously, using the
artemis queue updatecommand to modify queue attributes resulted in messages being lost or removed when the broker was restarted. This issue occurred because the ID of the queue was not preserved when the broker was restarted. This issue is resolved in the 7.0.3 release.
ENTMQBR-782 - Queue JMX properties not matching up
When running a version of AMQ Broker earlier than 7.0.3, it was possible under high load that the queue JMX attributes
Messages added, and
Message acknowledgedcould become out of sync. As a result, sometimes in AMQ Console, higher values for
Message acknowledgedwere displayed, while
Message countwas 0 and all messages were correctly consumed.
This issue is resolved in the 7.0.3 release. For more information, see Solution #3244211.
ENTMQBR-610 - Feature Last-Value Queue is not working with AMQP protocol
The Last Value Queue feature did not work with the AMQP protocol. This issue is resolved in the 7.0.3 release.
ENTMQBR-643 - Unable to log in to Hawtio console when the broker runs as a Windows service
When installing and running the broker as a Windows service, users were unable to log in to the management console. This issue is resolved in the 7.0.2 release.
ENTMQBR-506 - Hawtio console stops working after backup node goes from live to backup.
In a previous Beta release, a bug that prevented the HawtIO console from being usable on a back-up server existed. The issue occurred only if that server had been live before being relegated to a back-up. This issue is resolved in the 7.0.0 release.
ENTMQBR-498 - slow consumer: consumer is killed even though it receives at a rate higher than the threshold
In a previous Beta release, brokers using the AMQP
slow-consumer-*parameters could incorrectly close consumers that met the configured thresholds after the first scan interval. The issue is resolved in the 7.0.0 release.
ENTMQBR-77 - Expand error tree list
In a previous Beta release, attempting to 'expand all nodes' or the reverse in the left hand tree of the console produced no result. Users had to step through the tree manually. This issue is resolved in the 7.0.0 release.
For additional details about issues resolved in specific releases, see the following articles: