RHEA-2015:1879 - Product Enhancement Advisory

Topic

Red Hat Enterprise MRG Messaging 3.2 packages that include a number of bug fixes and enhancements are now available for Red Hat Enterprise Linux 6.

Description

Red Hat Enterprise MRG is a next-generation IT infrastructure incorporating Messaging functionality. It 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 AMQP messaging broker; AMQP client libraries for C++, Java JMS, and Python; as well as persistence libraries and management tools.

These updated packages for Red Hat Enterprise Linux 6 include numerous bug fixes and enhancements for the Messaging component of MRG.
Space precludes documenting all of these changes in this advisory. Users are directed to the Red Hat Enterprise MRG Messaging 3.2 Release Notes document for information on the most significant of these changes: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/3/html/3.2_MRG_Messaging_Release_Notes/index.html

Users of the Messaging capabilities of Red Hat Enterprise MRG 3.2, which is layered on Red Hat Enterprise Linux 6, are advised to upgrade to these updated packages, which provide numerous bug fixes and enhancements.

Solution

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

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise MRG Messaging 3 x86_64
• Red Hat Enterprise MRG Messaging 3 i386

Fixes

• BZ - 1015448 - AMQP 1.0 qpid::messaging c++ local transactional support to be enabled (Transactions not yet supported)
• BZ - 1066256 - [LinearStore] changing efp size after using store broke the new durable nodes creation
• BZ - 1082591 - [Selectors] selector containing only spaces fails
• BZ - 1099448 - Several connection options are missing in the doc
• BZ - 1123778 - [ACL] Python client demands unnecessary permission / performs unnecessary actions
• BZ - 1128783 - Minor logging usability improvements, very low risk.
• BZ - 1131720 - HA logging improvements - log prefix with status and ID.
• BZ - 1136191 - qpid-ha -h or --help should exit with returncode of 0
• BZ - 1136418 - QMF Session name to contain user ID
• BZ - 1145145 - [AMQP 1.0] Incoming QMF objects dont update "transfers" counter
• BZ - 1148807 - [linearstore] Restarting broker with empty journal raises confusing warning
• BZ - 1150127 - AMQP 1.0 consumer should be able to get messages from browse-only queue
• BZ - 1151446 - Heartbeats for AMQP 1.0 Qpid Messaging API
• BZ - 1152012 - [linearstore] missing journal id in "trace Mgmt create journal." log
• BZ - 1152032 - purging TTL expired messages via purge task should not increase acquires counters
• BZ - 1152686 - qpid-winsdk should support Microsoft Visual Studio 2012
• BZ - 1155540 - Raise error or shutdown broker when --sasl-config is invalid path
• BZ - 1155553 - qpid-tool to halt when initial connection to broker failed
• BZ - 1158903 - [linearstore] segfault when 2 journals request new journal file from empty EFP
• BZ - 1160367 - [linearstore] Add ability to use disk partitions and select per-queue EFPs
• BZ - 1163650 - [linearstore] segfault when EFP tries to generate new journal but ulimit prevents it
• BZ - 1167911 - [linearstore] Symlink creation fails if store dir path is not absolute
• BZ - 1170775 - starting qpidd causes 5 different SELinux AVCs
• BZ - 1181005 - receiver.fetch raises KeyError after network glitch
• BZ - 1192924 - A broker configured with disabled authentication requires authentication from a client connected from Windows
• BZ - 1201334 - Qpid python client hangs when message with routing key longer than 255 is sent (mutual recursion)
• BZ - 1204094 - Traceback "broker closed connection: 541" appears in different cases
• BZ - 1207368 - NullPointerException from Hello example (hello.properties file missing)
• BZ - 1208585 - Not supported qpid-config option "--generate-queue-events" in a list of options
• BZ - 1215806 - Provide qpid JMS client that supports AMQP 1.0
• BZ - 1224300 - [MRG 3.2] linearstore raising JERR_LFCR_SEQNUMNOTFOUND after sending many DTX transactions
• BZ - 1234423 - Outdated "README-winsdk.txt" file
• BZ - 1240552 - No error info logged for io errors with ssl
• BZ - 1241525 - Document ACL user connection limit
• BZ - 1245128 - Qpid-jms amqp 1.0 client can not receive messages from MRG-M broker
• BZ - 1245184 - [amqp1.0] exceeding queue size limit causing empty message to be enqueued instead of rejecting
• BZ - 1249942 - [docs] Heartbeats for AMQP 1.0 Qpid Messaging API
• BZ - 1254588 - AMQP 1.0 jms client hangs when another reconnect should happen on the same MRGM broker
• BZ - 1254944 - update AMQP 1.0 selector filter handling to accept JMS Header names and align with client JMSType behaviour
• BZ - 1254948 - Incorrect evaluation of NOT IN and BETWEEN when types mismatch
• BZ - 1258971 - qpidd selector issues when parsing of certain integer literals
• BZ - 1258993 - connections to qpidd fail if SASL is used

CVEs

(none)

References

• http://www.redhat.com/security/updates/classification/#normal