Subject | Re: [firebird-support] Server do not notice client disconnections |
---|---|
Author | Helen Borrie |
Post date | 2006-10-20T01:03:22Z |
At 04:44 AM 20/10/2006, you wrote:
server recognises that the connection has gone
and will proceed to clean up outstanding
resources and terminate the dead process. This
note in the firebird.conf file should help you if
you want to alter your system's socket timeout configuration:
# 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 instructions of this article:
# http://support.microsoft.com/default.aspx?kbid=140325
./hb
>We´re using FB 1.5 CSIt already does so. After a period of time, the
>
>The server has about 200 simultaneous connections during work day.
>
>The problem is that sometimes users have problems on their PCs or the
>client app must be terminated via Task Manager -- and -- what happens
>is that the FB server do not 'notice' the client app have terminated
>so the fb_inet_server process keep runing.
>
>Is that any way to make FB server shut this processes or is this
>feature planned for future FB releases ?
server recognises that the connection has gone
and will proceed to clean up outstanding
resources and terminate the dead process. This
note in the firebird.conf file should help you if
you want to alter your system's socket timeout configuration:
# 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 instructions of this article:
# http://support.microsoft.com/default.aspx?kbid=140325
./hb