> Hello,
>
> we have a problem that is periodically happening on customers side every 1
> or 2 weeks. We are using Jaybird 2.1.3 with Firebird 2.1.3 Classic (64
> bit) on a Windows Server 2008 R2 machine.
>
> As described in subject, java threads are frozen in our application with
> the following stacktrace :
>
> java.net.SocketInputStream.socketRead0(Native Method)
> java.net.SocketInputStream.read(SocketInputStream.java:129)

This means it is reading from the server and hasn't received the data yet, and therefor is blocking until it receives data. This could mean that Firebird server is not sending data (frozen, working on a sweep); it could also mean that Jaybird is expecting more data than it should.

I believe that Jaybird 2.1.3 does not have a read timeout configured, so it will block indefinitely if it does not receive a reply. Roman could probably tell you more.

Mark
--
GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit
gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl