--- In Firebird-Java@yahoogroups.com, Mark Rotteveel <mark@...> wrote:

>
> On 14-5-2013 20:07, hugo.larson wrote:
>
> > I have upgraded to FB 2.5 and the firebird.log is flooded with:
> >
> > TYCO-DA15A15021 (Server) Tue May 14 12:05:56 2013
> > INET/inet_error: read errno = 10054
>
> Error 10054 is connection reset by peer. That error indicates that the
> connection wasn't closed properly before the socket was closed. This can
> happen if Connection.close() was never called (or failed) before the
> Connection object is garbage collected or the application terminated.
>
> In theory it could also mean that something else (eg overactive
> firewall) is closing/resetting sockets. If you are using a
> connectionpool, it might also indicate that the connectionpool is not
> properly shutdown before the application terminates (and the sockets of
> the connections in the pool are closed).
>
> As long as you commit your transactions etc, this error is relatively
> benign; afaik it might just result in resources being in use longer both
> on the client and on the server.
>
> I also identified a problem where certain some exceptions during a
> statement prepare will result in Jaybird not properly closing the
> connection (JDBC-291). I didn't fix that in Jaybird 2.2 yet, I will
> schedule a backport to 2.2.4.
>
> I am looking for similar problems (the current wire protocol
> reimplementation is a good starting point).
>
> Mark
> --
> Mark Rotteveel
>

Hi,

Yes it seems to be the case. When the JVM is exited the log occurs.

Does Jaybird have a static call to close all open connections?

Thanks,