RHEA-2011:0890 - Product Enhancement Advisory

Topic

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

Description

Red Hat Enterprise MRG is a next-generation IT infrastructure incorporating
Messaging, Realtime, and Grid 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 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.

These updated packages for Red Hat Enterprise Linux 5 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 2 Technical Notes document for information on the most
significant of these changes:

https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html/Technical_Notes/

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

Solution

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

This update is available via 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 5 x86_64
• Red Hat Enterprise MRG Messaging 2 for RHEL 5 i386

Fixes

• BZ - 453538 - [RFE] Support for message priority
• BZ - 484218 - Need for configurable LVQ property
• BZ - 484691 - Qpid RDMA support doesn't work with iWarp RNICs
• BZ - 500430 - Feature: Support SASL on inter-broker links
• BZ - 547743 - Add ability to create queues, exchanges and bindings between them via QMFv2
• BZ - 569918 - Support ssl client options for qpid::messaging::Connection
• BZ - 581560 - Deleting a queue binding may leave stale federation routes.
• BZ - 585844 - RFE: allow timed autodelete for queue
• BZ - 606357 - Support for dropping messages first by priority, then by age within priority
• BZ - 611820 - qpid-stat -c always shows "msgOut" as zero
• BZ - 614944 - qpidd broker crash in mrg::msgstore::TxnCtxt::abort() -> DbTxn::abort()
• BZ - 615300 - Failover exchange is not listed by management tools
• BZ - 621467 - messaging API does not allow acknowledging messages up to a particular point
• BZ - 629926 - qpid-winsdk an authentication example missing
• BZ - 632625 - Ring queue does not properly implement byte size limits
• BZ - 637127 - Sorting option for qpid-stat doesn't work on RHEL4
• BZ - 641822 - qpid-winsdk's qpid-perftest sometimes refuses to report throughput and end with 'Controller exception: Bad report: 1.#INF' for small message count (--count)
• BZ - 646913 - Java qpid-client ignores hostnames containing underscores
• BZ - 647858 - Qpid Messaging .NET Binding can not ack individual messages.
• BZ - 652233 - qpid tools bad behaviour if PLAIN authentication is forced
• BZ - 653167 - qpid-config doesn't show all queues in broker
• BZ - 653923 - C++ Client does not set "redelivered" flag on retransmitted messages
• BZ - 654020 - Queue policy properties reported by QMF should match the real ones in the broker
• BZ - 654461 - QMF Method Calls Fail on New Queues
• BZ - 657398 - [RFE] Provide mechanism to alter brokers logging level at runtime
• BZ - 657523 - .NET example clients does not exit cleanly (warning Ignoring frame while closing connection)
• BZ - 658448 - qpid-winsdk csharp.map.receiver source example code typo (csharp.map.recevier.cs)
• BZ - 659071 - qpid::messaging::Connection:isOpen is non-const
• BZ - 660289 - [RFE] Configurable queue threshold alerts
• BZ - 660291 - [RFE] Producer flow control
• BZ - 663013 - Default address created by python client is durable
• BZ - 663022 - Address assertion do not work well if address type specified with python client
• BZ - 664486 - Queue reroute doesn't honor alternate exchange
• BZ - 666931 - .NET Binding to C++ Messaging is missing Receiver Get and Fetch Functions
• BZ - 667172 - JMS Client does not set "redelivered" flag on retransmitted messages
• BZ - 667428 - transactions atomicity violated by 'transparent' failover
• BZ - 667463 - Add tcp_nodelay option to python API
• BZ - 667771 - Cannot create a subscription on topic created for another JMS Provider, class of topic provided is: org.apache.qpid.client.AMQAnyDestination
• BZ - 667970 - RFE: provide incoming and outgoing message count statistics for connection
• BZ - 668580 - .NET Binding to C++ Messaging missing locks around resource destructors
• BZ - 671369 - RDMA client can segfault when no SASL mechanism specified
• BZ - 674005 - QueueReceiver does not work with new addressing
• BZ - 674390 - Buffer library does not prevent overflow when writing sequences of bytes.
• BZ - 674631 - After Rejections No Messages Received
• BZ - 674678 - Closed Receivers Do Not Delete Queues and Do Not Reroute Acquired Messages to Alternate Exchange
• BZ - 675921 - clustered qpidd broker fails ocassionly the cluster_tests.ShortTests.test_route_update
• BZ - 676345 - Running "qpid-config -a guest/guest@<host>" against a remote broker sometimes exists with exception (SessionException: ExecutionException(... description=u'unauthorized-access: authorised user id : anonymous@QPID but user id in message declared as guest)
• BZ - 679212 - Messages following a queue's Alternate-Exchange do not follow the exchange's Alternate-Exchange
• BZ - 679216 - Deleting a queue with an alternate exchange can cause infinite loop
• BZ - 679723 - The server example C++ application (server.cpp) requires an (second) input argument which is not used
• BZ - 680228 - [store] Deadlock in BDB database del() function
• BZ - 680477 - exchange.declare should throw a 404 - not found exception if the exchange type is unknown
• BZ - 680479 - message_cancel should throw 404 not-found exception if subscription does not exist
• BZ - 681026 - Clustered broker exits with invalid-argument error
• BZ - 681166 - Improve performance of map encoding into amqp in python qpid client
• BZ - 681279 - excessive per-connection memory
• BZ - 681313 - Qpidd Server crashes when implementing RDMA
• BZ - 681331 - Alternate-Exchange configuration not communicated between nodes in a cluster
• BZ - 682218 - exclusive, auto-delete queues not freed up in the broker on queue delete
• BZ - 684182 - [PACKAGING] python-qmf-debuginfo should obsolete qpid-cpp-mrg-debuginfo <= 0.9.1073306
• BZ - 690261 - Broker Federation broken after QPIDD restart
• BZ - 692132 - Assertion in AsyncCompletion during scalability tests
• BZ - 692134 - Help/Usage text for qpid-config is incorrect
• BZ - 693407 - Invalid client code will crash the broker daemon.
• BZ - 693895 - CyrusSasl ctor logic change for callback storage
• BZ - 694617 - alternate-exchange (in x-declare part of address) does not work from JMS
• BZ - 695263 - qpidd broker crashes under stress test in qpid::broker::SessionHandler::getConnection (this=0x0)
• BZ - 695353 - High level API addressing: Java client address parser throws java.lang.ClassCastException on valid address
• BZ - 695716 - C++ broker crash in DTX handling under stress test.
• BZ - 696373 - Provide a README for JMS examples
• BZ - 696637 - exchanges with IVE option cause cluster inconsistencies in updatees
• BZ - 696655 - cached exchange reference can cause cluster inconsistencies if exchange is deleted/recreated
• BZ - 696698 - binding order inconsistency in cluster
• BZ - 696974 - Problems in qpid-config --help
• BZ - 697913 - Deadlock between the failover mutex (in AMQConnection.java) and the current_exception_lock (in AMQSession.java)
• BZ - 698721 - durable messages transmission - performance issue (1.3.2 -> 2.0 candidate)
• BZ - 700822 - Producer flow control needs to be enabled for clustering.
• BZ - 701777 - Qmf Agent stuck in flow-stopped mode

CVEs

(none)

References

• https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html/Technical_Notes/