29. Release LBM 4.1.2 / UME 3.1.2 / UMQ 2.0 - November 2010

29.1.1. Bug Fixes

• Changed the resolver_unicast_interface option to accept either multicast-capable or non-multicast interfaces.

• Corrected a UM Gateway issue that could cause a peer portal to become deaf to a wildcard pattern, if the peer portal received a wildcard receiver topic query (WC-TQR) for the pattern before the companion portal was connected.

• Corrected a problem with the UM Gateway that prevented topics from being purged when no receivers existed for them. This was evident in the Web Monitor's Gateway page that showed more active topics than any of the individual portals.

• Corrected a problem with epoll initialization that prevented epoll from being used with ud_acceleration.

• Corrected a problem with the UM Gateway that created a deadlock if multiple, newly created sources immediately begin sending to a peer gateway.

• Corrected a segfault in a UM Gateway peer portal that might occur when a wildcard receiver has been deleted and the peer portal cancels interest in the deleted wildcard receiver's topic pattern.

29.1.2. Known Issues

• 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.

• When using LBT-IPC, a seg fault can occur when sending messages larger than 65,535 bytes when ordered_delivery has been set to 0 (zero). The seg fault occurs when fragments are lost. Setting transport_lbtipc_behavior to receiver_paced avoids the seg fault by eliminating loss. 29West is investigating this issue.

• When using the LBT-RDMA transport with Java applications, a segfault can occur if you kill a receiver with Ctrl-C. As a workaround, use the JVM option, -Xrs. 29West is investigating this problem.

• If you use the current version of VMS (3.2.8), LBM 4.1 issues the following warning: LOG Level 5: LBT-RDMA: VMS Logger Message (Error): vmss_create_store: 196[E] vms_listen: rdma_bind_addr failed (r=-1). This warning indicates that rdma_bind failed for ethernet interfaces, which is expected behavior. Currently, VMS attempts rdma_bind on all interfaces. When released, VMS version 3.2.9 will only run rdma_bind on infiniband-capable interfaces.

• When using Automatic Monitoring with ud_acceleration and the epoll file descriptor option, LBM may leave a monitoring thread running after context deletion. This situation produces the following error: VMA ERROR : epoll_wait_call:36:epoll_wait_call() epfd 48 not found. 29West is investigating this problem.

29.1.3. LBM 4.0 Changes

The following changes were implemented in LBM Release 4.0 but omitted from the LBM 4.0 Updated Features section. They have also been added to that section.

• Blocking sends from within a context-thread callback are no longer permitted and now return an LBM_EINVAL error. This restriction eliminates a possible deadlock. Non-blocking sends from a context-thread callback are still permitted, and any type of send is permitted outside a context-thread callback.

• Some API calls that were formerly never safe to call from within a context-thread callback (due to a deadlock condition) are now always safe to call from within a context-thread callback. These API calls include:

  • lbm_request_delete()

  • lbm_request_delete_ex()

  • lbm_response_delete()

  Additionally, the following send-related API calls are now safe to call from within a context-thread callback provided you set the LBM_SRC_NONBLOCK flag.

  • lbm_multicast_immediate_message()

  • lbm_multicast_immediate_request()

  • lbm_unicast_immediate_message()

  • lbm_unicast_immediate_request()

  • lbm_send_response()

• Added ability to set a LBM Configuration Option interface by name. When setting by name the configuration option's value must be wrapped in quotes.

29.2.1. New Features

• Added the following UME configuration options.

  • (source) ume_activity_timeout

  • (receiver) ume_activity_timeout

  • (source) ume_state_lifetime

  • (receiver) ume_state_lifetime

  • Also added new new topic ume-attributes options, source-state-lifetime and receiver-state-lifetime. See Options for a Topic's ume-attributes Element.

  The activity and state lifetime timers protect the Reg IDs of inactive sources and receivers and also controls how long UME retains the state and cache for inactive sources and receivers. These options can operate in conjunction with the proxy source option or independently. See Activity Timeout and State Lifetime Options for a discussion of these timers work together and how they work with proxy sources.

29.2.2. Bug Fixes

• Fixed an issue that could result in a crash from leakage of a proxy source object in the store leading to a "double free" of the proxy source object.

• Fixed a problem that could cause UME receivers to crash if their source goes down and comes back repeatedly with the same reg ID and also comes back registered to more stores than previously.

29.2.3. Known Issues

• Receivers using event queues and Spectrum with UME can experience a SIGSEGV while shutting down if events still exist on the event queue when it is deleted. As a workaround, use LBM_EVQ_BLOCK when dispatching event queues. During application shutdown, call lbm_evq_unblock() after deleting receivers associated with the event queue, but before deleting any context objects. Once the dispatch thread exits, it is safe to proceed with context deletion. 29West is working on a solution to this problem.

29.3.1. New Features

• JMS Support: Added support for JMS with the Ultra Messaging JMS. See Ultra Messaging JMS API Quick Start for information on running the example JMS client applications. See Ultra Messaging JMS API Guide for conceptual, operational and configuration information about Ultra Messaging JMS.

29.3.2. Bug Fixes

• Corrected a problem that could cause a fatal assert if a queue received a MIM message not meant to be queued on a topic that exists in the queue due to other messages that were meant to be enqueued.