77. Series 2.3 Releases

Fix to avoid unnecessary scheduling of the LBT-RU/RM rate controller once the retransmission rate limit has been reached.

Added ABI support for future binary compatibility

Bug fix for object deletion in JNI interface routines

Bug fix in the setting of application IDs used in LBM statistics monitoring

Added ABI support for future binary compatibility

Bug fix for object deletion in JNI interface routines

Bug fix in the setting of application IDs used in LBM statistics monitoring

Bug fix for race condition in LBT-RU/LBT-RM rate controller

Bug fix to prevent session messages from backing up the lead sequence number to a previous state

Bug fix for proper handling of immediate requests with long topic names on Solaris

Bug fix in lbm_license_str(); the input string is no longer modified in place.

Added dispose method to LBMMessage class in the Java API

Added Event Queue attribute queue_objects_purged_on_close to control whether the Event Queue is "purged" when various object types (source, receivers, requests, wildcard receivers, timers) are closed

Bug fix of off-by-one check for NAK buffer overflow

.NET namespace changed to com.latencybusters.lbm

.NET assembly (lbmcs.dll) signed with unique strong name

Changed behavior of object-specific getopt functions lbm_src_getopt()/lbm_src_str_getopt(), lbm_rcv_getopt()/lbm_rcv_str_getopt(), and lbm_event_queue_getopt()/lbm_event_queue_str_getopt() to return a value for all options regardless of whether they are settable via the corresponding setopt function

Added LBM version preprocessor definitions

Split liblbmj.so (lbmj.dll) from liblbm.so (lbm.dll)

Added statistics monitoring capability to C API

Added statistics monitoring capability to Java API

Added statistics monitoring capability to .NET API

Added LBM API functions to enable initialization of an LBM license from a string or file.

Changed default value for resolver_multicast_ttl from 1 to 16

Added a signature to verifiable messages (-V option) generated by example source programs, and checked for by example receiver programs. This prevents receivers, which are expecting verifiable messages, from incorrectly flagging every message from a non-verifiable message source as failing verification.

This change introduces an incompatibility (with regard to example programs using verifiable messages only) with previous releases. Example programs from earlier releases will not work with example programs from Release 2.3 (when using verifiable messages).