61. Release LBM 3.3 / UME 2.0 - February 2008

See also Release LBM 3.3EA3 / UME 2.0EA2 2008-1-11, Release LBM 3.3EA2 / UME 2.0EA1 2007-12-19 and Release LBM 3.3EA1 2007-11-15.

• Changed the default configuration settings for all 23 port configuration parameters in LBM. Each port default was moved by 10,000. For example, mim_destination_port moved from 4401 to 14401. The LBM code will use the original locations with the definition of the "LBM_USE_ORIG_DEFAULT_PORTS" environment variable (value not pertinent).

• Implemented Topic Sequence Number Information (TSNI) messages. These will be received from LBTRM/LBTRU sources that have been idle for more than the transport_topic_sequence_number_info_interval. Older receivers won't understand TSNI messages and will display the log message, "LOG Level 5: LBMC cntl unknown next header 20, ignoring header". This may be safely ignored.

• Added support for multiple LBM transport configuration parameters to be set through the lbmmon API.

• Added log message identifying the presence of multiple network interfaces before a specific resolver interface has been specified.

• Named all LBM data structs to support forward declaration.

• Added propagation of Java exceptions incurred during LBM callbacks back to JVM as LBMApplication exceptions.

• Changed LBM and UME to ignore insignificant whitespace in XML-based configuration files.

• Added file name and line number to memory allocation failure messages.

• Added better detection of invalid LBM configuration attribute names and values.

• Changed UME to flag instances where a store is not seeing topic advertisements from a source.

• Fixed bug in Java and .NET SDM LBMSDMField.sameBaseType() method which always returned true.

• Removed the fatal assertion on invalid sequence number checkin UME store that appeared when an unrecoverable loss burst message is received.

• Added failover optimization to UME store initialization.

• Fixed a race condition in the UME store with respect to source deletion and pending AIOs that could cause a crash.

• Added throttling of unrecoverable loss messages in the UME store log.