Subject | Re: [ib-support] 10054 errors in interbase.log |
---|---|
Author | Ann W. Harrison |
Post date | 2001-10-22T20:30:44Z |
Hi Rob,
WSAECONNRESET
(10054)
Connection reset by peer.
A existing connection was forcibly closed by the remote host.
This normally results if the peer application on the remote
host is suddenly stopped, the host is rebooted, or the remote
host used a "hard close" (see setsockopt for more information
on the SO_LINGER option on the remote socket.) This error may
also result if a connection was broken due to "keep-alive"
activity detecting a failure while one or more operations are
in progress. Operations that were in progress fail with
WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
It is possible that clients are timing out due to a problem in the remote
connection keep-alive code. I thought that was fixed in 0.94 - it certainly
is in the current version.
Regards,
Ann
www.ibphoenix.com
We have answers.
>The interbase log is getting a few 10054 errors. I cannot reproduce them.Firebird is returning the error code that INET returned to it:
>the error code is ISC335544726 Error Reading data from the connection.
WSAECONNRESET
(10054)
Connection reset by peer.
A existing connection was forcibly closed by the remote host.
This normally results if the peer application on the remote
host is suddenly stopped, the host is rebooted, or the remote
host used a "hard close" (see setsockopt for more information
on the SO_LINGER option on the remote socket.) This error may
also result if a connection was broken due to "keep-alive"
activity detecting a failure while one or more operations are
in progress. Operations that were in progress fail with
WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
It is possible that clients are timing out due to a problem in the remote
connection keep-alive code. I thought that was fixed in 0.94 - it certainly
is in the current version.
Regards,
Ann
www.ibphoenix.com
We have answers.