Chapter 7. Changes in 3.2.5

7.1. Errata

RHBA-2017:27935-02 – Red Hat Enterprise MRG Messaging 3.2.5 Release

BZ#1294824 - Allow qpid C++ client and broker to use TLS 1.1 and TLS 1.2
Previously, only Transport Layer Security (TLS) version 1.0 was supported for use by the broker and C++ client.
As a result, the code did not accept TLS 1.1 and TLS 1.2 as valid protocol versions.
The code has been updated to now support both TLS 1.1 and TLS 1.2 as valid protocol versions.
BZ#1315485 - [AMPQ1.0] Setting idle-timeout to ffffffff, broker fires infinite loop of ConnectionTicker with zero timeout
Setting idle-timeout to 0xffffffff on an incoming AMQP 1.0 connection caused broker to go into a loop.
As a result, messages were sent to the logfile and CPU usage increased.
The code generating timer events was corrected to handle this case.
BZ#1332143 - Broker fails to restart after sending too-big message into paged queue
If you had a durable paged queue configured and sent a durable message that was too large to fit into a single page, the broker rejected it, as expected. However, the rejected message was still written to disk, which was not expected.
If you then stopped and attempted to restart the broker, it failed with an error message.
The broker no longer writes a durable message to disk if it is too large to fit in a single page and the broker no longer fails to restart.
BZ#1359372 - [linearstore] overwrite-before-return causing latencies for broker's clients
When the overwrite-before-return option was used on journal files, overwriting the files took a significant amount of time.
Because of this delay, clients were blocked for seconds at a time.
The method used for overwriting journal files has been refactored. Customers should no longer notice a delay or client unavailability when using the overwrite-before-return option.
Report a bug