On Thu, 16 May 2013 07:47:24 -0000, "hugo.larson" <hugo.larson@...>
wrote:

> --- In Firebird-Java@yahoogroups.com, Mark Rotteveel <mark@...> wrote:
>>
>> On 13-5-2013 23:49, hugo.larson wrote:
>> >> It is good to know, but I am not yet closer to a solution ;)
>> >>
>> >> Could you try to reproduce the issue with Jaybird 2.2.3 and share

the

>> >> exception that should now include the IOException stacktrace?
>> >>
>> >> Mark
>> >>
>> > Hi Mark,
>> >
>> > Here is the Exception from Jaybird 2.2.3:
>> >
>>
>> > Caused by: java.net.SocketException: Socket closed
>> > at java.net.SocketOutputStream.socketWrite0(Unknown Source)
>> > at java.net.SocketOutputStream.socketWrite(Unknown Source)
>> > at java.net.SocketOutputStream.write(Unknown Source)
>> > at org.firebirdsql.gds.impl.wire.XdrOutputStream.flush(Unknown

Source)

>> > ... 59 more
>>
>> I will check for socket closes in the code, but nothing jumps out right

>> now and the areas where sockets are closed are really limited.
>>
>> Maybe the socket is already closed earlier because of a different

error.

>> If possible, could try and collect more of these errors and see if you
>> also get other IOExceptions than this one?

> Hello,
>
> So far the only Exception is Socket Closed. Will continue monitoring.
>
> Could be something in the DB engine that closes the socket?

I am not sure. In those cases I would actually expect a real error
returned from Firebird instead of just closing the connection. It could
happen if you use an UDF that crashes the server (this would be less
noticable for Classic Server than for SuperServer, as with classic it would
only affect a single connection).

Given the number of 10054 (connection reset by peer) errors you mentioned
in your other mail, it could also mean that something else
(virusscanner/firewall/proxy) is forcefully closing connections.

Mark