CONNECT_TIMEOUT - UEM Manager configuration option
- Stonebranch (Deactivated)
Analytics
Description
The CONNECT_TIMEOUT option specifies how long a Universal Event Monitor Manager will wait for a connection to a remote Universal Broker to complete.
CONNECT_TIMEOUT is particularly helpful when more than one host is specified for the REMOTE_HOST option. By default, connection timeouts are controlled by the TCP/IP stack. Depending on this value, it may take several minutes to process a list of hosts before a connection actually succeeds. Setting a CONNECT_TIMEOUT value allows connection attempts to unreachable Universal Brokers to fail quickly, decreasing the time required to process a list of one or more hosts.
Note
CONNECT_TIMEOUT is most beneficial when set to a value that is less than the TCP/IP stack's default timeout, which is implementation dependent. A relatively small CONNECT_TIMEOUT value is recommended, to make sure it — and not the TCP/IP default — is applied.
Usage
Method | Syntax | IBM i | HP NonStop | UNIX | Windows | z/OS |
|---|---|---|---|---|---|---|
Command Line, Short Form | n/a | |||||
Command Line, Long Form | -connect_timeout seconds |
|
|
| ||
Environment Variable | UEMCONNECTTIMEOUT=seconds |
|
| |||
Configuration File Keyword | connect_timeout seconds |
|
|
|
Values
seconds is the time, in seconds, that the UEM Manager will wait for a connection to a Universal Broker to complete. This value applies to each host contained in the resolved, expanded, and scrubbed REMOTE_HOST list.
Valid values for seconds are 0 (zero) to 300.
Default is 0.
(This mean that each connection attempt will use the implementation-defined TCP/IP timeout value. This is the behavior of connection attempts prior to version 3.2.0 of Universal Event Monitor.)
If the time specified by seconds elapses before a successful connection to a Universal Broker on the specified system is established, the UEM Manager will select the next host in the list. If no more hosts are available, the application will end with an error to indicate that no connection was made.
Note
It is possible for the total time required to attempt connections to all hosts in the REMOTE_HOST list to exceed the number of seconds specified in this option.