54. Release LBM 3.3.7 / UME 2.0.5 - September 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.

Removed source IP address from LBT-RU receiver filtering criteria to avoid message loss caused by messages sent from the wrong interface.

Implemented mechanisms to preallocate a given number of SDM fields to improve efficiency (Java and .NET).

Added context request_tcp_bind_request_port configuration option to allow a context to be created that does not bind the request port. This option can be used when Request/Response, Late Join, Unicast immediate reception, or UME capabilities are not needed.

Fixed problem that prevented source advertisements from being sent after any sort of advertising socket send error.

Allow the receiver resolution_number_of_sources_query_threshold to be set to zero to effectively disable the sending of topic queries from a particular receiver.

Added Java and .NET LBMContext.scheduleTimer() methods that hold a reference to the LBMTimer object by the LBMContext to ensure that the LBMTimer object does not get garbage-collected prior to expiration.

Provided new application callback function for wildcard receivers that will be called when the messaging framework discovers a source publishing on a topic matching a receiver's wildcard pattern. This functionality also supports application logic to configure attributes specific to the underlying new receiver object for that topic.

Removed lbmcssdm.dll dependency on lbmcs.dll.

Created LBMSDM jar containing only SDM classes.

Added LBMReceiver.receiverCount() method to return the number of callbacks registered to a given receiver.

Added LBMSDMRawTimestamp.get_sec() and .get_usec methods to .NET and Java SDM.

Fixed looping condition caused by internal recursive use of SDM LBMSDMArrayMessage.get_len() method.

Implemented delivery_control_maximum_total_map_entries attribute to limit the amount of memory utilized by the receiver delivery controller. This was left undone by reimplementation of the receiver delivery controller in a prior release.

Fixed NullReferenceException that occurs when .NET LBMMessage.topicName() or LBMMessage.source() called in EOS handling code.

Fixed /dev/poll usage problem which causes a fatal assertion: "[fdm->devpoll_last_result>=0] at line 2121 in ../../../../src/lib/lbm/lbmfds.c"

Fixed transport_[lbtrm | lbtru]_source_socket_buffer implementation to pick-up OS default if OS default is larger (as documented).

Fixed problem related to copying of SDM blobs (Java and .NET only).

Improved performance of Java and .NET SDM string handling.

Implemented additional debug facility to use LBM_DEBUG_ASSERTFILE environment variable to direct dump of in-core debug data after fatal assertion.

Fixed formatting of Uint64 (Java) and float/double (.NET) SDM fields.

Fixed cloning of SDM message arrays (Java and .NET only)

Fixed LBM.SRC_EVENT_WAKEUP under Java which was previously not being delivered after an LBMEWouldBlockException.

Fixed handling of large numbers of transports sessions to avoid segmentation fault.

Provided additional synchronization to avoid unexpected exception related to the use of an Event Queue with Java and .NET string caching (problem originated in LBM 3.3.6).

Prevented bogus topic query from being emitted from .NET wildcard receivers even when wildcard topic queries are disabled (problem originated in LBM 3.3.6)

When registering a file descriptor using epoll, previous releases would fatally assert with the message: fatal assertion (epoll_err==0) line 1034 lbmfds.c in function lbm_fd_register whenever an error was returned. This has been changed to either print a log message when epoll returns EBADF (Tried to register a bad file descriptor) or ENOENT (Tried to perform an operation on a socket that is already closed). All other error types will still fatally assert.

Fixed two memory leaks that occurred during context deletion. The first leak was 72 bytes and occurred after deleting a context that had been used with an LBM source. The second leak varied in size depending on the topics cached by the context. It occurred after a receiver was deleted and then the associated context was deleted before the current resolver_query_interval had expired.

Added support for UME store daemon on Solaris 5.10.

Fixed a problem with source re-registration that caused the source to start sending with the wrong sequence number. This problem occurred when a source had not sent any data before it re-registered with the store. The source misinterpreted the registration information it received from the store and did not start sending with sequence number zero. Receivers would appear deaf during long retransmit request generation intervals waiting for sequence number zero.

Corrected a problem that prevented the Solaris UME store from cleaning up cache and state files for inactive sources and receivers due to failed TCP keepalive connections from the Solaris UME store to clients.