44. Release LBM 3.5.2 / UME 2.2.2 - August 2009

Improved performance of all 29West products on Microsoft® Windows® by implementing new build techniques.

Microsoft has recently provided a security update for the C runtime library (msvcr80.dll version: 8.0.50727.4053). In order to avoid potential issues, 29West recommends installing the latest redistributable C runtime library. See http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=766a6af7-ec73-40ff-b072-9112bab119c2 for further details.

Corrected a problem with Java that could cause a JVM crash if a thread received a small response message (less than 8192 bytes) followed by a large response message (greater than 8192 bytes).

Fixed a problem with Late Join that occurred when recovering old messages from a source. If loss occurred on the live stream during recovery, the source would either stop or delay the delivery of messages to the application and buffer the messages instead, causing unbounded memory consumption. In addition, any messages that were delivered could be delivered out of order.

Corrected a memory leak that occurred when creating Java LBMContextStatistics objects.

Corrected a problem with the LBT-IPC transport on Microsoft Windows that caused multiple processes that were started in rapid succession to send data to the same shared memory area. This problem produced the following failed assertion at the receiver: MUL_ASSERT((MUL_SQN_GT(sqn, ctlr->stream_high_sqn)));

Fixed an issue with SDM Unicode strings in .NET. If a Unicode field was the last field in a packet, the length check produced an assertion because the check was made during the unicode string encoding rather than before the encoding. The length check now occurs prior to string encoding.

Increased an internal NAK timer constant for LBT-RM receivers to improve loss handling in high-loss cases.

Added a protective check to prevent a segfault when a source sends with monitoring enabled and resolver_multicast_incoming_address set to 0.0.0.0.

When using Event Queues with the Java API on Mac OS X kernel 9.4, core dumps have occurred. Mac OS X kernel versions prior to 9.4 have not produced this behavior. 29West is investigating this issue.

Fixed a problem when recovering messages from a UME store identical to the Late Join problem cited above. If loss occurred on the live stream during recovery, the UME store would stop or delay the delivery of messages to the application, buffering the messages and causing unbounded memory consumption. In addition, any messages that were delivered could be delivered out of order.