53. Release LBM 3.3.8 / UME 2.0.6 - October 2008

Known Issue: 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.

Feature Suspension: String caching for the Java and .NET APIs has been temporarily disabled due to unstable operation. In addition, for the setSourceNotificationCallbacks in Java and .NET (LBMReceiverAttributes), LBM temporarily ignores the value returned from the source creation callback. Relevant calls to retrieve this object will return NULL. String caching and full setSourceNotificationCallbacks functionality will be re-enabled in a later release.

Added the Source_Paced value to the transport_tcp_multiple_receiver_behavior option. TCP senders can now send as fast as they can without regard to the speed of the receivers. This may cause lost messages.

Fixed memory corruption problem in Java API which caused crashes during cleanup of transport sessions on 32-bit systems for receivers using LBM Event Queues.

Corrected a fatal assertion ("map!=NULL") on an LBT-RU source caused when using Source Side Filtering (SSF) that resulted from deleting a receiver which had not completely connected to the corresponding source.

Fixed a race condition in the Java API that occurred when a context is closed that allowed LBMTimers to be constructed without appropriate callbacks.

Fixed a race condition in the .NET API with LBMContext.scheduleTimer() which could result in callbacks not being executed for very short duration timers because the timers would expire before their callbacks had been registered. Timer callbacks are now registered before the timer is actually scheduled.

Fixed a race condition in the .NET API which could cause crashes or deadlocks when calling LBMContext.close().

Fixed an issue in the .NET API caused by marshalling data between managed and native code. Data was being lost after being passed down to native code, which lead to deadlocks in very rare cases.

Fixed a very small memory leak (~40 bytes) when deleting an LBM context on Microsoft® Windows®. A mutex used for MIM was not being freed.

Reverted LBMTimer.cancel() method in Java API to take no arguments. An overload of the cancel() method which took a boolean argument was inadvertently added in LBM 3.3.7 in place of the original method. This meant that users of 3.3.7 had to call LBMTimer.cancel(false) instead of LBMTimer.cancel().

Added LBM log warnings when connection disconnects or connection deletion occurs when data exists in the send queue.

Added the new LBM Configuration option, transport_tcp_activity_method to support the ability for receivers on TCP transports to use TCP keepalive support in the Operating System for determining transport session liveness.

Corrected a problem with the LBM Gateway running on Microsoft Windows that prevented traffic from being sent across a filtering gateway.

Corrected a problem with Multicast Immediate Messaging (MIM) sends when the rate limiter is exceeded so that it no longer indefinitely blocks.

No specific UME problems were discovered.