Stephen
Thanks for the info.
Jeff
mysteriously quit working after a few weeks of being on version 4 of
Vantage.
Kbase Id:
18415
Title:
Using Clienttimeout Parameter Correctly
Title: Using the ClientTimeout Startup Parameter Correctly
KnowledgeBase number: 18415
Creation Date: 11/25/98
Modified Date: 11/25/98
Modified Date: 12/06/99
This document applies to: ClientTimeout Parameter
Version and Release Number: 7.3B + NT database server products
Summary: 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. There is also an enhancement request submitted
to make this a startup parameter that will be accepted at the command
line.
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.0 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.
The -clienttimeout server startup parameter is planned for a future
commercial release, although version and date are not confirmed as
yet. When introduced the existing ClientTimeout parameter will no
longer be valid in the registry or the progress.ini file.
References To Written Documentation or Other KnowledgeBase Documents:
SAG 15-17
-----Original Message-----
From: jhouse@... [mailto:jhouse@...]
Sent: Tuesday, March 06, 2001 11:58 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] ClientTimeOut(free version) has stopped
I was wondering it the procedure for revision 8 is the same for revision 9.0
B
Thanks
Jeff House
MIS Coordinator
Airtronics Metal Products
1980 Senter Road
San Jose, CA 95112
(408) 977-7817
Jhouse@...
http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/webkb.htm
l?TAB=dsp&kbid=17953
Progress includes this in their software.
Kbase Id:
17953
Title:
Detecting dead remote clients
Detecting dead remote clients
Many of our users ask how a Progress server detects a dead remote
client.
Progress cannot detect a dead remote client. There is no watchdog.
Progress relies on the network protocol (TCP, SPX, NETBIOS, etc...)
to notify the database that a remote user has died or disconnected.
If a dead remote client is not being removed from the database, the
network stack is not notifying the Progress database. In many cases
a patch or upgrade to the networking protocol will fix the problem.
However, on NT there is a ClientTimeOut Progress parameter you can
use. It 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.
In version 7 of Progress on NT the ClientTimeOut parameter should be
put in the [Startup] section of the progress.ini file. In version 8,
it should be put in the [Startup] section of the registry:
HKEY_CURRENT_USER\Software\PSC\PROGRESS\<ver>\Startup
The syntax is:
ClientTimeOut=n
where n is the number of minutes a client can be idle before theserver
disonnects it.
Unix and VMS systems have a KeepAlive option which functions in much
the same way. KeepAlive is a TCP setting, not a Progress parameter.
Please see the following knowledgebase articles for more detailed
information:
13493 Socket KeepAlive Q&A, disconnecting of remote clients
16001 KeepAlive functionality on VMS
16429 KeepAlive option for NT server
17130 How to set the socket KeepAlive on HPUX
-----Original Message-----
From: Todd Hofert [mailto:thofert@...]
Sent: Tuesday, March 06, 2001 11:53 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] ClientTimeOut has stopped
If it is the Client Timeout Utility that Michael Podlin wrote it probably
quit working because you have recently performed a Vantage client install
which replaced the .vtg file with default settings which do NOT point to the
ClientTimeout Utility. You would need to re-edit your .vtg file.
Hope this helps
Todd Hofert
Spartan Graphics, Inc.
(616)887-8243
-----Original Message-----
From: Stephen Freeman [mailto:stephenf@...]
Sent: Tuesday, March 06, 2001 11:35 AM
To: Vantage E groups (E-mail)
Subject: [Vantage] ClientTimeOut has stopped
The ClientTimeOut feature that is available in Progress 9.0B has suddenly
quite working here. We where using it to disconnect remote dead clients.
Does anybody have any ideas why it would quite working?
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Yahoo! Groups Sponsor
Click Here to Find Software Faster
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Yahoo! Groups Sponsor
Click Here to Find Software Faster
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
Thanks for the info.
Jeff
>>> stephenf@... 03/06/01 11:06AM >>>More detail about the ClientTimeOut feature is given in Kbase# 18415. Ours
mysteriously quit working after a few weeks of being on version 4 of
Vantage.
Kbase Id:
18415
Title:
Using Clienttimeout Parameter Correctly
Title: Using the ClientTimeout Startup Parameter Correctly
KnowledgeBase number: 18415
Creation Date: 11/25/98
Modified Date: 11/25/98
Modified Date: 12/06/99
This document applies to: ClientTimeout Parameter
Version and Release Number: 7.3B + NT database server products
Summary: 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. There is also an enhancement request submitted
to make this a startup parameter that will be accepted at the command
line.
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.0 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.
The -clienttimeout server startup parameter is planned for a future
commercial release, although version and date are not confirmed as
yet. When introduced the existing ClientTimeout parameter will no
longer be valid in the registry or the progress.ini file.
References To Written Documentation or Other KnowledgeBase Documents:
SAG 15-17
-----Original Message-----
From: jhouse@... [mailto:jhouse@...]
Sent: Tuesday, March 06, 2001 11:58 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] ClientTimeOut(free version) has stopped
I was wondering it the procedure for revision 8 is the same for revision 9.0
B
Thanks
Jeff House
MIS Coordinator
Airtronics Metal Products
1980 Senter Road
San Jose, CA 95112
(408) 977-7817
Jhouse@...
>>> stephenf@... 03/06/01 10:16AM >>>Actually it isn't. Progress includes a timeout utility look at
http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/webkb.htm
l?TAB=dsp&kbid=17953
Progress includes this in their software.
Kbase Id:
17953
Title:
Detecting dead remote clients
Detecting dead remote clients
Many of our users ask how a Progress server detects a dead remote
client.
Progress cannot detect a dead remote client. There is no watchdog.
Progress relies on the network protocol (TCP, SPX, NETBIOS, etc...)
to notify the database that a remote user has died or disconnected.
If a dead remote client is not being removed from the database, the
network stack is not notifying the Progress database. In many cases
a patch or upgrade to the networking protocol will fix the problem.
However, on NT there is a ClientTimeOut Progress parameter you can
use. It 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.
In version 7 of Progress on NT the ClientTimeOut parameter should be
put in the [Startup] section of the progress.ini file. In version 8,
it should be put in the [Startup] section of the registry:
HKEY_CURRENT_USER\Software\PSC\PROGRESS\<ver>\Startup
The syntax is:
ClientTimeOut=n
where n is the number of minutes a client can be idle before theserver
disonnects it.
Unix and VMS systems have a KeepAlive option which functions in much
the same way. KeepAlive is a TCP setting, not a Progress parameter.
Please see the following knowledgebase articles for more detailed
information:
13493 Socket KeepAlive Q&A, disconnecting of remote clients
16001 KeepAlive functionality on VMS
16429 KeepAlive option for NT server
17130 How to set the socket KeepAlive on HPUX
-----Original Message-----
From: Todd Hofert [mailto:thofert@...]
Sent: Tuesday, March 06, 2001 11:53 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] ClientTimeOut has stopped
If it is the Client Timeout Utility that Michael Podlin wrote it probably
quit working because you have recently performed a Vantage client install
which replaced the .vtg file with default settings which do NOT point to the
ClientTimeout Utility. You would need to re-edit your .vtg file.
Hope this helps
Todd Hofert
Spartan Graphics, Inc.
(616)887-8243
-----Original Message-----
From: Stephen Freeman [mailto:stephenf@...]
Sent: Tuesday, March 06, 2001 11:35 AM
To: Vantage E groups (E-mail)
Subject: [Vantage] ClientTimeOut has stopped
The ClientTimeOut feature that is available in Progress 9.0B has suddenly
quite working here. We where using it to disconnect remote dead clients.
Does anybody have any ideas why it would quite working?
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Yahoo! Groups Sponsor
Click Here to Find Software Faster
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Yahoo! Groups Sponsor
Click Here to Find Software Faster
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]