Hello, Leonardo!

Friday, September 16, 2011, 10:26:59 PM, you wrote:

LC> On Fri, Sep 16, 2011 at 12:56 PM, Ann Harrison <aharrison@...>wrote:

>> > Eventually we turned to the log file generated by Firebird and found
>> > numerous reports of this error INET/inet_error: read errno = 10054
>> >
>> > According to the network guys the network is stable, but we cannot verify
>> > that.
>> The usual source of errno = 10054 (and it's Unix-ish cousin) is that a
>> client program exited without closing its database connection, either
>> through an unfortunate code branch or by killing the application.

LC> Is this Windows 64 or 32 bit?

no difference. "numbered" errors in Firebird log comes "outside"
Firebird. For example, 10054 is a socket error on Windows (any).

The cause of these errors (socket errors and 10054) can be:
- bad or incompatible network hardware. can be tested only with
hardware testers or special "sniffer" software. These type of
problems usually can't be dectected by, for example, copying files over network.

- Firewall, proxy, antivirus. These type of programs (and other ones)
intercept tcp sockets and can break them, limit their number in system, and even
prevent Firebird to listen to client requests.

- keepalive setting (Windows, Linux). Need to be tuned on some
systems. http://support.microsoft.com/kb/813827


--
Dmitry Kuzmenko, www.ib-aid.com