At 02:37 PM 3/1/2001 +0800, Brian Dunstan wrote:

>Now I know I've seen some really useful looking documentation on
>interbase.log somewhere... wish I could find it now.

Try ibphoenix.com - it's probably there somewhere.

>I am troubleshooting a strange (so far un-reproducible) problem where
>transactions seem to be rolled back unexpectedly, without any exception
>being generated. While sniffing around for clues I found these errors in
>interbase.log:
>
>MHS_SRV01 (Server) Thu Mar 01 10:38:31 2001
> INET/inet_error: read errno = 10054
>...
>Windows SDK says:
>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.)

That error ordinarily means that the client killed his process (or
shutdown his PC) while it was connected to the database. That would
account for the transaction rollback without an error, but would not
explain the mystery. If I were you, I'd beat the users until they
admit their malfeasance - though that discourages repeat business.


Regards,

Ann
www.ibphoenix.com
We have answers.