Added support for intentional gaps in Hot Failover message streams. See Hot Failover Intentional Gap Support. Also added support for Hot Failover optional messages that HF receivers can be configured to receiver or not receive. See Hot Failover Optional Messages.
Corrected a problem that could cause a crash of an initiator UM Gateway configured with a single-TCP peer connection if the acceptor gateway was not yet running.
The configuration option delivery_control_maximum_total_map_entries was not being applied on a per thread basis when use_transport_thread was set as intended. This option is now applied correctly on a per thread basis.
When setting the configuration options delivery_control_loss_check_interval and use_transport_thread together, the loss check timer started on the incorrect thread and subsequently produced the Fatal Assert orderrec->msg!=NULL or crash. This timer is now scheduled on the correct thread.
Corrected a cross-version problem that could cause a fatal assert when an application deletes a UMS 4.X receiver that has received data from a UMS 3.X source.
Added defensive measures in the UM Gateway to guard against the delayed delivery (tens of seconds) of internal events after they have been enqueued, possibly due to CPU starvation.
Corrected a problem in the UM Gateway which could result in a deadlock when using a single-TCP peer connection (either acceptor or initiator).
Corrected a format specifier in a debug log statement for LBT-RU sources which could lead to a segfault.
Corrected a problem in the UM Gateway that prevented a topic matching a pattern from being immediately forwarded. This only occurred when there were at least 3 topic resolution domains, the source was accessible only via a peer connection from one domain, and wildcard receivers specifying overlapping but different patterns existed in the other two domains.
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. This situation produces the following error: VMA ERROR : epoll_wait_call:36:epoll_wait_call() epfd 48 not found. 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).
When using the UM Gateway on Microsoft® Windows®, single-TCP acceptor peer portals and TCP peer portals do not work. This issue will be corrected in a future release. Please contact us at http://29west.com/support for more information.
No specific UMP problems were discovered.
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.
No specific UMQ problems were discovered.
| Prev | Home | Next |
| Release LBM 4.2.6 / UME 3.2.6 / UMQ 2.1.6 - June 2011 | Release LBM 4.2.4 / UME 3.2.4 / UMQ 2.1.4 - May 2011 |
Copyright (c) 2004 - 2014 Informatica Corporation. All rights reserved.