49. Release LBM 3.5.ea2 - April 2009

Introduced Interprocess Communication (IPC) LBM transport that allows sources to publish topic messages to a shared memory area managed as a static ring buffer from which receivers can read topic messages. For more information, see Transport LBT-IPC in LBM Design Concepts. See also Transport LBT-IPC Operation Options in the LBM Configuration Guide.

Added support for the kqueue fd_management_type on Mac OS X.

Added ability to set resolver_multicast_incoming_address to 0.0.0.0, eliminating incoming topic resolution traffic, which is useful for MIM-only contexts.

Significantly improved performance of Java receivers by taking advantage of some newer features of modern Java virtual machines. Embedded mode is now fully supported in Java with the same performance as sequential mode.

Allowed Intel Core Duo T2600 CPU machines to use high resolution timers instead of gettimeofday.

Removed the finalizer from LBMTimer Java class; changes in LBM 3.4 made the finalizer unnecessary.

Fixed a problem that caused the string "unknown" to be returned from a call to lbm_context_attr_str_getopt() for the context attribute fd_management_type if it was set to either epoll or devpoll, rather than the string epoll or devpoll, respectively.

Fixed a race condition where a .NET source event callback supplied to the LBMSource() or LBMContext.createSource() constructors had a chance of not being called for an event that occurred before the constructor returned.

Fixed a problem that prevented lbmmon from reporting LBM stats using lbmsnmp or UDP transport on .NET. When the lbmmon src was created, the LBM transport was used regardless of the value passed in for the transport parameter.

Fixed a display problem that reversed multicast addresses in warnings regarding LBT-RM transport sessions on little-endian machines. Also removed warnings for transport_session_maximum_buffer for LBT-RM and LBT-RU transports as this option affects TCP transports only.

Corrected a problem in LBM that resulted in a Segmentation Fault when using more than one thread to dispatch an event queue. One or more of the dispatching threads was able to access information associated with an event after the memory had been freed by another thread processing another event.

Corrected a problem in Java and .NET that could result in a failed assertion when using more than one thread to dispatch an event queue. One or more of the dispatching threads was able to access memory that had already been freed as a result of processing the End of Session (EOS) event on a different thread.

Corrected a problem in LBM that resulted in a Segmentation Fault when performing a delete operation on a source, receiver, or context in parallel with dispatching an event from an event queue. The dispatching thread was able to access information associated with an event after the memory had been freed by the delete operation.

LBM now correctly applies the resolution_number_of_sources_query_threshold option to receivers created in a Context that already has a source for the same topic.

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.