20. Release LBM 4.2.7 / UME 3.2.7 / UMQ 2.1.7 - July 2011

20.1.1. Bug Fixes

• Corrected a problem for 32-bit Java applications only, which resulted in the getStores() method of the LBMSourceAttributes class returning incorrect registration IDs or throwing an exception stating Store entry registration ID was < 0.

• Fixed an issue that could cause the logging of an IllegalArgumentException in Java applications when receiving responses.

• Fixed an issue with Late Join that caused a late joining receiver to send extra, unnecessary late join requests to a source, which resulted in spurious unrecoverable loss events on the receiver at the beginning of a late join.

20.1.2. Known Issues

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

20.2.1. Bug Fixes

No specific UMP problems were discovered.

20.2.2. Known Issues

• Receivers using event queues and Spectrum with UMP 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.

20.3.1. Bug Fixes

No specific UMQ problems were discovered.