15. Release UMS 5.1 / UMP 5.1 / UMQ 5.1 - November 2011

Added the message property object that allows your application to insert named, typed metadata to topic messages and implement functionality that depends on the message properties. UMS allows eight property types: boolean, byte, short, int, long, float, double, and string. See Message Properties Object for more.

Added the functions, lbm_hf_rcv_topic_dump(), lbm_hfx_attr_dump(), lbm_hfx_dump(), and lbm_hfx_rcv_topic_dump(), in the C API to dump the attributes of HFXs, HFX receivers, and hot failover receivers. Also added corresponding functions in the Java API and .NET API to dump attributes of HFXs and HFX receivers.

Improved multi-thread locking algorithms for Multi-Transport Threads to eliminate the possibility of receiver (or wildcard receiver) creation or deletion returning error EOP due to locking contention of the transport threads. Lock contention no longer requires an application to retry receiver creation or deletion.

Corrected a memory leak in the UM Gateway that occurred when an endpoint portal was unable to send a message.

Corrected a problem with the UM Gateway that occurred if the gateway was stopped and restarted. In this event, certain unicast control messages to destination contexts which were currently unknown to the gateway were dropped, but no effort was made to locate those destination contexts. Now those messages are still dropped, but the gateway sends queries to locate the destination context.

With ud_acceleration turned ON for VMA support in Infiniband, receivers are unable to resolve sources from within the same process. Similarly, sources are unable to discover themselves within the same process. No resolution issues exist if sources and receivers run in different process. Informatica is investigating this issue.

Late join initiated from receivers in a context configured for Multi-Transport Threads (MTT) will not work through the UM Gateway if the gateway is configured to forward late join traffic. Informatica is investigating this issue.

Hot Failover is not currently supported with Multi-Transport Threads.

Configuring sources with LBT-RU, source-side filtering, and adaptive batching may cause a crash. All three options must be set to cause the problem. Informatica is working to address this issue.

When using the UM Gateway Informatica recommends that you do not enable the Multi-Transport Threads feature. Informatica does not support nor test the operation of Multi-Transport Threads across the UM Gateway.

Multi-Transport Threads do not support persistent stores (UMP) or queues (UMQ).

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. Informatica is investigating this issue.

Sending LBT-IPC messages larger than 65,535 bytes is not supported when ordered_delivery has been set to 0 (zero) unless you set transport_lbtipc_behavior to receiver_paced.

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. Informatica is investigating this problem.

If you use the current version of VMS (3.2.8), UMS 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, UMS may leave a monitoring thread running after context deletion. Informatica is investigating this problem.

The UM Gateway does not currently support responses that exceed the maximum datagram size.

At the present time, 32-bit applications cannot interact with 64-bit applications using the LBT-IPC transport. As a result, a 64-bit UM Gateway cannot interact with a 32-bit application using LBT-IPC. It can only interact with a 64-bit application. Likewise, a 32-bit UM Gateway can only interact with a 32-bit application.

The UM Gateway does not currently support queuing at this time, only streaming and persistence. This will be resolved in a future release.

The UM Gateway is not supported as a standalone Windows service at this time. This will be resolved in a future release.

The UM Gateway does not currently support a four gateway "full-mesh" configuration (i.e., all gateways connected).

If using LBT-RDMA across the UM Gateway and you exit the gateway with Ctrl-C, you may see a segfault. Informatica is aware of this and has not observed any ill effects from this segfault.

Informatica recommends against configuring UM Gateways in a ring of peer portals - use configurations utilizing gateway endpoints (parallel paths) to break the ring.

Informatica recommends not stopping and restarting UM Gateways within the transport's activity timeout period (transport_*_activity_timeout defaults to 60 seconds for LBTRU and LBTRM).

Although UMS 5.0 applications should run well with LBM 4.2 UM Gateways, all Gateways should always run the same version.

Enabled the use of the UMM API that allows you to programmatically create and store application configurations in the UMM database. The UMM GUI uses the same API to create users, passwords, applications configurations and configuration templates. See UMM Java API for UMM objects, constructors and methods.

Corrected a problem with the UMM GUI Permissions dialog box that caused the dialog box to be deleted after rearranging the column headings.

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.

When running a store on a Solaris machine, you may experience registration failures after a few minutes. The store repeatedly reports the error, [WARNING]: wait returned error 4 [select: (22) Invalid argument]. Changing fd_management_type to devpoll prevents this problem. Informatica is investigating this problem.

UMP proxy source elections can only occur among stores in the same topic resolution domain connected directly via peer links. Informatica is investigating this problem.

Added support for the JMS message properties specification through the UM JMS API.

Fixed an issue with UMQ indexed queuing from a Java source that prevented the queue from sending correctly which produced the following exception: com.latencybusters.lbm.LBMEInvalException: UMQ index too long.