|Subject||Re: [firebird-support] Getting INET/inet_error: read errno = 10054|
Thanks. Very usefull feedback.
On 26-8-2016 22:27, Jardar Maatje jardar.maatje@...
> We are running fb 2.5.6 and are getting the INET erorr regularily.
> The error has been there before as well with earlier versions of fb.
> Is this something I should be conserned about and what can I do about it?
Error 10054 is "Connection reset by peer", which means that the server
tried to do something with the network connection from a client, and it
was already closed. This can happen due to network problems, or the
application was terminated abruptly. However the usual main cause is
that connections aren't properly closed, either by your applications (eg
you never close connections, and they are eventually terminated by the
garbage collector), or maybe by the driver you use (eg because its
implementation of a connection close is wrong).
> Another issue is that when I list transactions I have a transaction that
> is "stuck" back in time but that has no attachemnt associated with it.
> Is this normal?
> This is the row from the MON$TRANSACTIONS that have no corresponding
> MON$ATTACHMENTS row:
> 648583083 84322 0 26.08.2016, 19:11:47.489 648583083 648563078 649285961
> 2 -1 1 0 1 26 00000023:00000004
Assuming the normal order of columns in MON$ATTACHMENTS:
This is transaction 648583083 of attachment 84322, in state 0 (active),
it has READ_COMMITTED_VERSION isolation, wait without timeout (AFAIK),
read-only, no autocommit, with autoundo.
Maybe the associated attachment got terminated abruptly and Firebird
hasn't yet detected this and rolled back the transaction (or in this
case as it is read only: committed it). If you want to speed it up: a
restart of the Firebird server process would mark it as such IIRC.