Subject | Re: [firebird-support] Re: fastest dummy query |
---|---|
Author | Artur Anjos |
Post date | 2004-03-19T22:59:35Z |
Hi Harry,
This time is on Firebird 1.5, 2 hours.
Look at this info from firebird.conf:
--------------
#
# Seconds to wait on a silent client connection before the server sends
# dummy packets to request acknowledgment.
#
# DO NOT USE THIS OPTION. It may hang or crash Windows on the client
side as
# explained here: http://support.microsoft.com/default.aspx?kbid=296265
# or may not prevent eventual inactive client disconnection for other OS.
#
# 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
#
# Type: integer
#
#DummyPacketInterval = 0
--------------
Artur Anjos
> We think it is the linux firewall, that drops inactive tcpFrom time to time, a Fb server try to check if client it's still alive.
> connections after 30 min. I'm also not sure if the v1.03 had this
> also or is it new to v1.5. The Firebird server probably just closes
> the socket after the connection is dropped by firewall (nothing in
> the server log), client computer has the 10054 messages in the log
> file after each disconnect.
This time is on Firebird 1.5, 2 hours.
Look at this info from firebird.conf:
--------------
#
# Seconds to wait on a silent client connection before the server sends
# dummy packets to request acknowledgment.
#
# DO NOT USE THIS OPTION. It may hang or crash Windows on the client
side as
# explained here: http://support.microsoft.com/default.aspx?kbid=296265
# or may not prevent eventual inactive client disconnection for other OS.
#
# 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
#
# Type: integer
#
#DummyPacketInterval = 0
--------------
Artur Anjos