Dead sessions and timeouts

Category:
Databases - DBISAM

Knowledgebase Article:
(From a newsgroup posting on elevatesoft.public.dbisam, 12-1-2003)
Non C/S installations is not an issue - if the client goes away the file server will clean up the locks fairly quickly, at least with a Windows file server. As for C/S, if you want dead sessions with active locks to get cleaned up quickly, then configure the database server to have a low dead session expiration time (30 seconds is okay) and a connection timeout around 3 minutes (you probably don't want to go any lower than 1 minute). Then, in the application configure the remote session(s) so that RemotePing is True, RemotePingInterval to 1 minute, and RemoteTimeout to 3 minutes or more. This will ensure that the client application keeps pinging the server every minute unless it dies, in which case the server will kill the session after the connection timeout setting on the server (the 3 minutes above).
Tim Young

400 reads

Post new comment

Your name: *

E-mail: *

The content of this field is kept private and will not be shown publicly.

Homepage:

Subject:

Comment: *

Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <hr> <sup>  <blockquote>
Lines and paragraphs break automatically.
You can use context links in the text to create context-related links to pages or sites that provide additional information about a word or phrase.
Glossary terms will be automatically marked with links to their descriptions
Web and e-mail addresses are automatically converted into links.
Textual smileys will be replaced with graphical ones.
Scripture references will be linked automatically to an online Bible. E.g. John 3:16, Eph 2:8-9 (ESV).
You may link to webpages through the weblinks registry

More information about formatting options