The LBM Gateway allows you to configure the use of blocking or non-blocking sends on the outbound direct side. The default is to use non-blocking sends. If a send blocks when using non-blocking sends, the message is dropped and the receiver is notified of loss; the notifying mechanism is the same one that notifies when a message exceeds the inbound Event Queue size or delay parameters.
Avoid an array underflow that occurs when empty lines are encountered in configuration files.
Fixed header parsing to prevent spurious messages, sent to an LBM/UME port, from forcing LBM/UME into an infinite loop.
Fixed problem to prevent crash that occurs when debug logging is enabled on 64-bit Windows systems running 32-bit binaries.
Added support for the response_tcp_interface context configuration attribute to specify TCP interface for outgoing response connections. Allow non-multicast capable interfaces (e.g., loopback) to be accepted by request_tcp_interface.
Added the number of the failed port to bind-failure log messages.
Fixed the condition where a receiver using arrival order delivery always drops the first message, if it is a fragment.
Corrected condition that could cause a fatal assertion (fdm->poll_fds!=NULL) when fd_management_type is set to 'poll'.
Copyright (c) 2004 - 2014 Informatica Corporation. All rights reserved.