Subject | Re: [Firebird-Java] Re: GDS Exception. 335544721. Unable to complete network request to host |
---|---|
Author | Mark Rotteveel |
Post date | 2013-05-14T19:35:04Z |
On 14-5-2013 20:07, hugo.larson wrote:
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
> I have upgraded to FB 2.5 and the firebird.log is flooded with:Error 10054 is connection reset by peer. That error indicates that the
>
> TYCO-DA15A15021 (Server) Tue May 14 12:05:56 2013
> INET/inet_error: read errno = 10054
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