Timeout

The adapter will attempt to read from a socket until the timeout value is exhausted. In order to allow the adapter to check for a shutdown, due to channel timeout or the queue manager being shut down, the actual socket timeout is set to the Non-blocking timeout. The timeout value is then decremented by the non-blocking timeout until it is exhausted and is thus used as the overall timeout. Once the timeout value has been reached, the retries value is then decremented as described below.

The UDP/IP adapter uses the timeout value to determine the amount of time the adapter should wait for an acknowledgement. The timeout should be set to the time it takes a packet to flow across the network from initiator to responder. It is further suggested that multiple pings are undertaken with the packet size appropriate for the particular network. For instance if a + b is equal to the amount of time taken by the packet for the round trip, MQe assumes that a = b, the timeout should be set to the value of a. The UDP/IP adapter sends the value of the timeout across the network when setting up a conversation; the maximum value for the UDP/IP adapter is 4294967295.
Java™
Default value is TCP/IP 5 seconds, UDP/IP 10 seconds.
Set using Java property com.ibm.mqe.adapters.MQeCommunicationsAdapter.timeout.
The value should represent the time in milliseconds.
Native
Default value 10 seconds.
Set using Windows® Registry: HKEY_LOCAL_MACHINE > SOFTWARE > MQe > CurrentVersion > Communications > socketTimeout. The value is a string and should represent the time in milliseconds.

Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.