New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firebird.conf Client Connection Settings [DOC87] #6776
Comments
I will bring this up again. The suggested settings in the OS (/proc/sys/net/ipv4/tcp_keepalive_* and instrutions of article in Windows (by the way the article is no longer exists at this link)) are global to the OS and affects to all applications. Needed more sophisticated tools to set up Firebird connections.
If needed a more detailed explanation of the need, then the next article does it well - When TCP sockets refuse to die. This Oracle document - Dead Connetion Detection describes their configuration approach based on the same TCP options. Similarly, Postgres also has the ability to customize these options in the server configuration file postrgres.conf:
Сan be reproduced with isql:
|
Submitted by: Andrew Ayre (communicare)
The comments in Firebird.conf for client connection settings include:
# Normally, Firebird uses SO_KEEPALIVE socket option to keep track of
# active connections. If you do not like default 2-hour keepalive timeout
# then adjust your server OS settings appropriately. On UNIX-like OS's,
# modify contents of /proc/sys/net/ipv4/tcp_keepalive_*. On Windows,
# follow instrutions of this article:
# http://support.microsoft.com/default.aspx?kbid=140325
This microsoft article mentioned is only applicable to Windows 95 and NT. It does not seem to be possible to adjust server settings in Windows 7.
Can someone confirm this? I would like to reduce the keepalive timeout from the default 2 hours to 5 mins.
Thanks,
Tom
The text was updated successfully, but these errors were encountered: