RHBA-2014:1682 - Bug Fix Advisory

Topic

Updated Messaging component packages that fix multiple bugs are now available
for Red Hat Enterprise MRG 2 for Red Hat Enterprise Linux 6.

Description

Red Hat Enterprise MRG (Messaging, Realtime, and Grid) is a next-generation IT
infrastructure for enterprise computing. MRG offers increased performance,
reliability, interoperability, and faster computing for enterprise customers.

MRG Messaging is a high-speed reliable messaging distribution for Linux based on
AMQP (Advanced Message Queuing Protocol), an open protocol standard for
enterprise messaging that is designed to make mission critical messaging widely
available as a standard service, and to make enterprise messaging interoperable
across platforms, programming languages, and vendors. MRG Messaging includes an
AMQP 0-10 messaging broker; AMQP 0-10 client libraries for C++, Java JMS, and
Python; as well as persistence libraries and management tools.

This update fixes multiple bugs. Documentation for these changes will be
available shortly from the Technical Notes document linked to in the References
section. All users of the Messaging capabilities of Red Hat Enterprise MRG 2 are
advised to upgrade to these updated packages, which resolve the issues noted in
the Red Hat Enterprise MRG 2 Technical Notes. After installing the updated
packages, stop the cluster by either running "service qpidd stop" on all nodes,
or "qpid-cluster --all-stop" on any one of the cluster nodes. Once stopped,
restart the cluster with "service qpidd start" on all nodes for the update to
take effect.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise MRG Messaging 2 for RHEL 6 x86_64
• Red Hat Enterprise MRG Messaging 2 for RHEL 6 i386
• MRG Grid Execute 2 x86_64

Fixes

• BZ - 860691 - Poor performance when a priority queue with a ring queue policy has a large backlog
• BZ - 1121615 - An attempt to enqueue&dequeue a message with "too high priority" to a ring queue causes broker segfault
• BZ - 1128654 - nextReceiver() with IMMEDIATE duration always returns null
• BZ - 1132395 - Memory leak when using federation with unreliable link
• BZ - 1136294 - Memory leak when purging priority ring queue
• BZ - 1142866 - Purging TTL expired messages 5times longer than before
• BZ - 1147968 - Session.nextReceiver() with IMMEDIATE duration does not raise exception when connection is closed

CVEs

(none)

References

• https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_MRG/2/html/Technical_Notes/index.html