Myles Wakeham wrote:

>> On 30-Aug-2008 08:08:27, firebird-support@yahoogroups.com wrote:
>> What kind of network is between client and the server (you mentioned
>> using a client on a Windows box, and server is Linux)? Is it direct
>> connection via LAN, or you go through something like Internet, ADSL,
>> VPN, whatever?
>
> I'm connecting to the servers that are running on colocated boxes from my
> home network for testing.

Ok, we're getting somewhere now. The problem you have looks very similar
to various NAT-related network problems. After a period of inactivity,
some of the network nodes between client and server decides that one of
the hosts has stopped communicating, and 'frees' it's connection pool by
killing the connection.

Here at home I'm on a cable Internet broadband

> connection with about 6mb/s down and 1mb/s up.
>
>> Check the output of this command:
>>
>> # cat /proc/sys/net/ipv4/tcp_keepalive_time
>
> It returns 7200. I'm not sure how that is measured, but is this a
> measurement in seconds?

Yes, seconds. But, that's 2 hours. IIRC, you wrote that connection goes
down after 10 minutes of inactivity?

>> Also, are you sure the problem is on the server? There are some Windows
>> firewall software that also closes the connection after some idle time.
>
> No, the clients that have been connecting to Firebird also have access to
> Windows servers running FB 1.5.5 Super Server as well, and they are not
> experiencing this timeout at all.

Are the Windows servers part of the same network as the Linux ones?

BTW, you might also want to check TcpNoNagle and DummyPacketInterval
settings in firebird.conf. TcpNoNagle should be the default 1, and you
can play with DummyPacketInterval - altough it should not be used ;) -
just to see if that would help.

--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com