Kbase 18415: Using Clienttimeout Parameter Correctly
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/03/2003 |
|
Solution ID: 18415
GOAL:
How to use the ClientTimeOut Startup Parameter
FACT(s) (Environment):
Progress 7.3x
Progress 8.x
Progress 9.x
Windows
FIX:
In version 7.3B, a new startup parameter, ClientTimeout, was introduced. This parameter allows the server process to determine whether a client has been inactive for a specified period of time, and if so, the server disconnects the client and backs out any related active transactions. The parameter does not work as currently documented, however the functionality is there. This is not available as an online startup parameter. There is a doc bug entered for 9.0B and earlier releases.
Step by step details:
The parameter uses the following syntax:
ClientTimeOut=n
where n is the number of minutes a client can be idle before the server disconnects it.
This Clienttimeout parameter can be put into the registry in one of the following keys, by default this key will not exist so will need to be created.
HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\<VERSION>\STARTUP
or
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS\<VERSION>\STARTUP
where <version> is the current version (e.g. 8.3A).
Regardless of how you start the server, command line or ProControl, the ClientTimeOut parameter can be set in the progress.ini file or the registry. If the registry key exists, the progress.ini file is ignored. This means that if the key exists and you want the ClientTimeout functionality it must be set in the registry. If you want to use a progress.ini file to set this parameter then you must remove the registry key. As of version 8.2 of Progress, which introduced the use of the registry with Progress, and the ini2reg conversion tool, the registry entries take precedence over the contents of the ini file.