| Subject | Re: [firebird-support] Re: fb_inet_server.exe never died after a network error |
|---|---|
| Author | Helen Borrie |
| Post date | 2010-02-16T20:28:53Z |
At 12:11 AM 17/02/2010, you wrote:
The tricky part is that, like a lot of Windows defaults, it doesn't have a Registry entry. I would have to Google to find the MSDN KB paper that tells you which keys you have to create in registry - best if you search for it yourself and match up your Windows version with the appropriate KB paper.
If it's Linux then both the default timeout setting and the location of the file containing these settings is likely to be variable according to what distribution you are running on the server. Again, Google should be your friend here.
./heLen
>Greetings All,It is a setting in your server's TCP/IP configuration. By default, on Windows, it is 4 hours, i.e., 240 minutes if I remember rightly. The Firebird server process doesn't regard lost connections as "dead" until after this timeout has elapsed.
>
>I have the same problem on our network. We are still using Firebird 1.53 currently. Hope to upgrade later this year.
>
>Is there a Keep-Alive Timeout for 1.53? If so where is it set?
The tricky part is that, like a lot of Windows defaults, it doesn't have a Registry entry. I would have to Google to find the MSDN KB paper that tells you which keys you have to create in registry - best if you search for it yourself and match up your Windows version with the appropriate KB paper.
If it's Linux then both the default timeout setting and the location of the file containing these settings is likely to be variable according to what distribution you are running on the server. Again, Google should be your friend here.
./heLen