- Issued:
- 2011-10-24
- Updated:
- 2011-10-24
RHBA-2011:1399 - Bug Fix Advisory
Synopsis
Red Hat Enterprise MRG Messaging 2.0 bug fix update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated Red Hat Enterprise MRG Messaging packages that fix several bugs are now
available for Red Hat Enterprise MRG 2.0 for Red Hat Enterprise Linux 6.
Description
Red Hat Enterprise MRG (Messaging, Realtime and Grid) is a real-time IT
infrastructure for enterprise computing. MRG Messaging implements the Advanced
Message Queuing Protocol (AMQP) standard, adding persistence options, kernel
optimizations, and operating system services.
Release Note: Customers who are using the qpid-cpp-server-xml module must be
subscribed to the following Red Hat Network channel in order to satisfy the XML
dependencies for this release: Red Hat Enterprise Linux Server Optional.
Customers who are using the qpid-cpp-server-cluster module must be subscribed to
the Red Hat Enterprise Linux High Availability channel in order to satisfy all
dependencies. If you encounter yum dependency problems, ensure that you are
subscribed to all of the required channels as detailed above.
This update fixes the following bugs:
- Due to a regression, a memory leak was introduced that prevented the broker
from correctly releasing messages. Consequently, the broker's memory footprint
grew indefinitely. A patch has been provided to address this issue, and the
memory leak no longer occurs in the described scenario. (BZ#728586)
- After the upgrade of MRG Messaging from version 1.2 to version 1.3, the qpidd
daemon terminated unexpectedly on some of the cluster nodes. With this update,
the broker code has been fixed to handle all cases when a faulty client sends
frames before completely opening the connection, thus fixing this bug.
(BZ#734608)
- Previously, specifying an invalid IP address for a destination broker caused a
repeatable file descriptor leak. A patch has been provided to address this
issue, and the file descriptor leak no longer occurs in the described scenario.
(BZ#732063)
- Prior to this update, when a large message (over 4KB) was sent from the
python-qpid client to the broker, the connection became unresponsive and other
clients were unable to connect to the broker. This bug has been fixed, and
clients no longer hang in the described scenario. (BZ#733543)
- Under heavy load, the broker generated a large number of timer late/overrun
warning messages. Though the messages themselves were usually inoffensive, the
time to log them individually caused long (up to several seconds) delays and
inflated log files. With this update, logging output for these messages has been
restricted to the "--log-enabled=info" option, thus preventing this bug.
(BZ#690107)
Users of the messaging capabilities of Red Hat Enterprise MRG 2.0, which is
layered on Red Hat Enterprise Linux 6, are advised to upgrade to these updated
packages, which fix these bugs.
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/kb/docs/DOC-11259
Affected Products
- Red Hat Enterprise MRG Messaging 2 for RHEL 6 x86_64
- Red Hat Enterprise MRG Messaging 2 for RHEL 6 i386
Fixes
- BZ - 690107 - Too many 'task overran' warnings in qpid broker logs
- BZ - 728586 - Broker memory bloat due to leak of messages.
- BZ - 733543 - Client freezes up when sending a large message
CVEs
(none)
References
(none)
Red Hat Enterprise MRG Messaging 2 for RHEL 6
SRPM | |
---|---|
qpid-cpp-0.10-8.el6_1.src.rpm | SHA-256: dcd5383a8affb33e3e6df7b724f85a8ad4a4557fb7aa8b9b7f6556c20a561f3c |
x86_64 | |
qpid-cpp-client-devel-0.10-8.el6_1.x86_64.rpm | SHA-256: 2ff24bb2b46c116426fb51e073814be4bdf055484c034ea0dc59e6b7d4662f57 |
qpid-cpp-client-devel-docs-0.10-8.el6_1.noarch.rpm | SHA-256: 11bdf954b8c13f8e10d5cae9918911b880ee301ba8b727dd8f4cd491fe5470b1 |
qpid-cpp-client-rdma-0.10-8.el6_1.x86_64.rpm | SHA-256: 3a793345f813123acefaa763542c69f2dd264ee305feffe3efb7c2e31d32f39b |
qpid-cpp-debuginfo-0.10-8.el6_1.x86_64.rpm | SHA-256: c71fe4107c25fec372df7ef8747359662336f97d81f287dfa6caf0b610bca101 |
qpid-cpp-server-cluster-0.10-8.el6_1.x86_64.rpm | SHA-256: 34b0cd72208e1f88758bd9578887fc579755b63c15fc2db2366f6a2a9c53deb7 |
qpid-cpp-server-devel-0.10-8.el6_1.x86_64.rpm | SHA-256: 87f842809a12d29849104c8ced0ac395a8d529b4681def7a6b9c40d49752fb5c |
qpid-cpp-server-rdma-0.10-8.el6_1.x86_64.rpm | SHA-256: 1d9597e4a50480827845d3c0d8fc5e2f2986d8d89ec865a34788b96cf84aa5ca |
qpid-cpp-server-store-0.10-8.el6_1.x86_64.rpm | SHA-256: f3d5ba0b8d8f4b84303b255afbd3a63ed171d5bf52e0d171f716aee882aa1740 |
qpid-cpp-server-xml-0.10-8.el6_1.x86_64.rpm | SHA-256: 09f29c96ade4d2161a1905c50e4e34990518abf2e693c5f8411579d8c1e76517 |
i386 | |
qpid-cpp-client-devel-0.10-8.el6_1.i686.rpm | SHA-256: 8613a6f70b130341e3321f2477f7dca24fcf485aca51b7992e5bb1dfe85a7a95 |
qpid-cpp-client-devel-docs-0.10-8.el6_1.noarch.rpm | SHA-256: 11bdf954b8c13f8e10d5cae9918911b880ee301ba8b727dd8f4cd491fe5470b1 |
qpid-cpp-client-rdma-0.10-8.el6_1.i686.rpm | SHA-256: 21081691788d556b837e958419d36581adcd52bf00b9ead2b21a9781da5ae3d4 |
qpid-cpp-debuginfo-0.10-8.el6_1.i686.rpm | SHA-256: 9626c6901bd12f9b20065e7f90338adab9c307bcadd6539446ecf8d50f10672e |
qpid-cpp-server-cluster-0.10-8.el6_1.i686.rpm | SHA-256: 28d51628e53a302ca5ac288dff9cd39087d81f2ffbad05330a312c080b5459ae |
qpid-cpp-server-devel-0.10-8.el6_1.i686.rpm | SHA-256: d81a300ecddd979a6745178ccbf64315e613a5c121b0a73605d43446eab58dc3 |
qpid-cpp-server-rdma-0.10-8.el6_1.i686.rpm | SHA-256: 86437e5a1c4871654c0c293110fbff1fee7465bff604140264998bac92f922f3 |
qpid-cpp-server-store-0.10-8.el6_1.i686.rpm | SHA-256: daa35795f61510970301270130081788b8016b0797f58212f0ae87e7fe914d84 |
qpid-cpp-server-xml-0.10-8.el6_1.i686.rpm | SHA-256: c6cf25fe423700b87c286b7be7a821e1e962a0210f633072d1332d1741911b42 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.