How Long does a Checkout Request Actually Take to Time Out When FLEXLM_TIMEOUT is Set?
Summary
The environment variable FLEXLM_TIMEOUT can be used to set the timeout value for FLEXenabled applications.
Synopsis
The environment variable FLEXLM_TIMEOUT can be used to set the timeout value for FLEXenabled applications when it attempts to connect to a license server port in the range 27000?27009. But how long does a checkout request actually take to time out when FLEXLM_TIMEOUT is set?
Discussion
The environment variable FLEXLM_TIMEOUT is documented in License Administration Guide or End User Guide as follows.
Windows only: Sets the timeout value a FLEXenabled application uses when attempting to connect to a license server port in the range 27000?27009. Values are in microseconds, within the range 0?2,147,483,647. The default setting is 100,000 microseconds.
When license path is set as @host or a license file with no port number specified on its SERVER line, if no license server is up and running on the default port range 27000-27009, the actual timeout period of a checkout request is approximately equal to (FLEXLM_TIMEOUT setting) x 10 ports (27000-27009) x 2 (if LM_A_RETRY_CHECKOUT is TRUE; or 1 otherwise).
Additional Information
Since the FLEXLM_TIMEOUT setting may also affect the start of license server and lmreread, when the specified license file/path does not have a fixed port number, you may want to make sure FLEXLM_TIMEOUT setting is cleared in such cases.
lmgrd may take some time to finish a detection process before it starts vendor daemon, which is approximately equal to (FLEXLM_TIMEOUT setting) x 10 ports (27000-27009).
C:> lmgrd -c license_file (no port number specified on its SERVER line)
...
10:59:15 (lmgrd) Detecting other license server manager (lmgrd) processes...
...
lmreread may take approximately the same time to complete a similar detection process.
C:> lmreread -c @host
lmreread - Copyright (c) 1989-2009 Acresso Software Inc. All Rights Reserved.
[Detecting lmgrd processes...]
...