RHEA-2014:1296 - Product Enhancement Advisory

Topic

Red Hat Enterprise MRG Messaging 3.0 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, 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 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.0 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.0.0_MRG_Messaging_Release_Notes/index.html

Users of the Messaging capabilities of Red Hat Enterprise MRG 3.0, 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.

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/site/articles/11258

Affected Products

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

Fixes

• BZ - 453539 - Support message selectors
• BZ - 572456 - [Feature request] Provide the possibility to choose the network interface to bind qpidd.
• BZ - 574571 - Python messaging client unusable after receiving a malformed message
• BZ - 588504 - [RFE] [MRG] Messaging broker to listen only on SSL port
• BZ - 654734 - .NET Binding class Address mishandles Name and Type fields
• BZ - 661500 - Connection option syntax is inconsistent across languages and documentation is ambiguous
• BZ - 663961 - Headers exchange doesn't compare integers correctly
• BZ - 672534 - qpid java client does not delete high level API address when "addr; {delete: receiver}" specified
• BZ - 691411 - [RFE] mechanism to detect when messages are overwritten in ring-type queues
• BZ - 696919 - Message sent by python producer can't be read with java consumer
• BZ - 697505 - Dynamically created bridge queues not always recreated after network outage
• BZ - 697966 - Consumption throughput decreases under increasing producer load
• BZ - 698325 - C++ Messaging .NET Binding: copied objects lead to obscure memory access violations.
• BZ - 699393 - Queue route bridge creation silently fails if source queue does not exist
• BZ - 703886 - Federation bridge doesn't recover from session errors
• BZ - 703891 - Deadlock when multiple threads concurrently operate on the same receiver
• BZ - 705015 - Message.setJMSMessageID() not compatible with ActiveMQ MessageID
• BZ - 705414 - TTL overflow
• BZ - 709325 - Possibility to create queue files dynamically and resizing queues without deleting them
• BZ - 710429 - qpid-cluster, qpid-tool and qmf-tool do not allow SASL mechanism to be chosen
• BZ - 710520 - Message TTL not adjusted correctly for messages about to expire
• BZ - 719589 - Python example "server" fails
• BZ - 728509 - Specifying username/password in JMS clients should not be mandatory
• BZ - 731725 - Closing a session after the connection was closed results in 100% CPU
• BZ - 733758 - Catch and report failure to open qpidd.sasldb when PLAIN authentication is enabled
• BZ - 740152 - Invalid handling of qpid.max_size
• BZ - 744040 - Released (and redundant) delivery records not removed
• BZ - 755651 - getJMSReplyTo does not return null for null ReplyTo property
• BZ - 756808 - qpid-stat -q output, "bytes" column overflow
• BZ - 758254 - The subscription queue is not removed after the link is closed
• BZ - 768114 - Enable TCP_NODELAY by default
• BZ - 771830 - Enable high resolution timestamps for qpidd logs using QMF and a qpidd option.
• BZ - 772028 - malfunctioning unsettled() receiver method
• BZ - 782070 - qpidd broker can start up without listening to a TCP port if SSL multiplexing is requested and given certificate not valid
• BZ - 784270 - AMQDestination equals() validation is broken for addresses
• BZ - 786167 - ruby QMFv1 console uses puts
• BZ - 790016 - Only string values for LVQ key are accepted
• BZ - 790390 - Qpid segfault while wallaby is connected
• BZ - 796765 - heartbeats not reliable as means of detecting loss of network in c++ client
• BZ - 797092 - Support log category exclusion
• BZ - 808105 - ACL syntax does not allow specifying '' exchange
• BZ - 823489 - qpid-config always sends journal parameters to broker
• BZ - 824985 - Federated links become stale after source broker host fails
• BZ - 824988 - [RFE] Federated link heartbeat interval is hard coded to 120 seconds
• BZ - 828442 - When sending a message, Java client gets unauthorized-access error due to using "ILADDRESS=<emailaddr>" as the user-id
• BZ - 845999 - second invocation of createConsumer fails for queue in JNDI properties file
• BZ - 848170 - Qpid daemon does not warn about unknown config options
• BZ - 859119 - Potential HA broker message duplication when deleting a queue with an alt-exchange
• BZ - 862899 - [RFE] Extend the qpidd --wait option to work at shutdown
• BZ - 865689 - "Recovery found" logs of wrong severity
• BZ - 872111 - qpid-config traceback in case of ACL denial
• BZ - 873674 - Durable messages with ttl behaviour.
• BZ - 873883 - Dynamic federation bindings can become out-of-sync
• BZ - 874516 - [RFE] Per-user configurable limit on the number of active connections
• BZ - 880360 - HA replication of propagated bindings can lead to incorrect configuration
• BZ - 885207 - Move all qpid config files under the qpid config dir
• BZ - 888449 - Perl language bindings not properly mapping uint8_t type
• BZ - 889552 - HA broker deadlock after loss of primary broker
• BZ - 890532 - NullPointerException raised in AMQDestination.equals method
• BZ - 894375 - --tcp_nodelay broker option to have yes/no values
• BZ - 895515 - '--ssl-key' option missing in several management tools
• BZ - 895937 - Link cannot be deleted/closed by QMF in Failed state
• BZ - 896570 - retries parameter ignored for the very first broker
• BZ - 904010 - connectdelay parameter ignored for the first broker in brokerlist
• BZ - 906814 - qpidd --help does not list --sasl-config option default
• BZ - 908224 - reconnect_timeout ignored in qpid.messaging.Connection()
• BZ - 909829 - qpid-receive does not commit ready address message
• BZ - 910512 - qpidd's header exchange binding argument evaluation is not functional for qpid c++ client[s]
• BZ - 912519 - broker ignores if_empty and if_unused flags when deleting queues
• BZ - 913448 - invoking Receiver::fetch() in a loop for slow producer causes only first <prefetch> messages received
• BZ - 915774 - qpid-tool to have -b option as other qpid tools
• BZ - 915821 - RFE: Support per user queue quotas in ACL file
• BZ - 919017 - XML exchange does not update statistics when no binding key matches routing key
• BZ - 949014 - Setting --ack value on Federation links forces a fixed finite credit limit.
• BZ - 949530 - Give C++ broker on unix ability to import a listening socket opened by parent process
• BZ - 949533 - Change Threshold Alerts from Level-Sensitive to Edge-Triggered
• BZ - 950501 - python clients throw "[Errno 1] _ssl.c:1217: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry"
• BZ - 955578 - Multi-threaded fetching messages from different queues causes fetch delay
• BZ - 955674 - ACL delete action should not ignore object's properties other than name
• BZ - 959446 - Several mistyped connection options in the API documentation
• BZ - 959447 - missing 'protocol' connection option description in the messaging api doc
• BZ - 960049 - qpid-latency-test reports it cannot achieve desired sending rate every second measurement
• BZ - 961014 - Variant decoding/conversion incorrect for at least bin8, int8, uint8 data types
• BZ - 964228 - amqp1.0: User shall be warned when using wrong syntax in the address string
• BZ - 970668 - qpid segfaults in qpid::ha::BrokerReplicator::disconnected
• BZ - 975949 - max-negotiate-time feature breaks AMQP 1.0 (and arguably doesn't achieve the desired objective anyway)
• BZ - 976398 - Broker segmentation fault when closing, if ever created a queue federation link
• BZ - 977290 - README-winsdk.txt file contains a link to non existing web page
• BZ - 977374 - qpid-tools help typos (CRAM-MD -> CRAM-MD5)
• BZ - 978135 - Message.setJMSMessageID() error message is incorrect
• BZ - 1009493 - Client succeeds to connect to non-ssl broker even if the ssl transport is requested by the client
• BZ - 1018746 - released message is not marked as redelivered
• BZ - 1018749 - When a message is browsed the redelivered flag is always set to true
• BZ - 1024528 - QPID-5275 HA transactions failing in qpid-cluster-benchmark
• BZ - 1024832 - C# client conecting on SSL raises unhandled exception
• BZ - 1024972 - bind using qpid-config succeeds on exclusive queue
• BZ - 1027385 - connection creation event not raised and authIdentity not set
• BZ - 1029446 - Invalid message filter on purge is ignored
• BZ - 1030219 - C++ client on Windows connecting a broker via AMQP 1.0 protocol fails
• BZ - 1032487 - Add ability create, delete and list objects of arbitrary types with qpid-config
• BZ - 1039550 - Broker maximum allowed connections option only works when acl enabled
• BZ - 1041574 - Python client deletes subscription queue even if it was declared to not be exclusive
• BZ - 1049359 - Deleting paged queue does not remove underlying file
• BZ - 1049376 - Creating paged queue can overwrite existing qpidd files
• BZ - 1049498 - [amqp1.0] connection loss is not detected by session sync() call
• BZ - 1051441 - Broker segfault when wrong filter used
• BZ - 1052046 - QMF to track queue owner (userId)
• BZ - 1053758 - Java client ignores missing heartbeats
• BZ - 1053761 - exception thrown from select when signal received
• BZ - 1055583 - ACL property/properties for paged queues
• BZ - 1056157 - HA primary broker does not go active if there are no replicated queues.
• BZ - 1056635 - [AMQP 1.0] Session::nextReceiver() not working
• BZ - 1060202 - Set timeout for every DTX transaction
• BZ - 1061754 - qpid-ha set --backups fails
• BZ - 1062173 - Remove qmf-tool from qpid-tools package
• BZ - 1064410 - qpid-config to remove legacystore queue journal options
• BZ - 1069757 - Can't disambiguate name for which both queue and exchange exist
• BZ - 1082023 - An exchange is deleted by a request for topic removal
• BZ - 1082487 - [Selectors] prefix key is not selected
• BZ - 1085053 - [AMQP1.0] Broker crash on remove domain request after unsuccessful interconnect attempt (to unreachable broker)
• BZ - 1088003 - heartbeat interleaved with message frames causes decode error
• BZ - 1090368 - [Selectors] does not recognize redelivered message with amqp.redelivered
• BZ - 1090376 - [Selectors] statement LIKE ESCAPE does not reject '%' and '_' as escape char
• BZ - 1090395 - [Selectors] ExactNumeric and ApporoxNumeric does not accept prefix + sign
• BZ - 1097559 - Federated link ends up in Connecting state forever after connecting to shutting down broker
• BZ - 1097848 - rerouting messages to non-local filtered queue crashes broker
• BZ - 1100442 - Need to change Selector from singleton to singleton per process (QPID-5637)
• BZ - 1122856 - ambiguous nodes: the queue is removed by exchange removal request
• BZ - 1122857 - ambiguous nodes: queue is not created if the exchange of the same name exists
• BZ - 1126952 - ssl framing error on inter-broker connection
• BZ - 1128653 - nextReceiver() with IMMEDIATE duration always returns null
• BZ - 1129277 - C++ example "server_reconnect.cpp" cannot be built

CVEs

(none)

References

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