Hi,

> I'm not using PoolMon or another Connection-Manager, just the
> standard DriverManager.getConnection().
> I'm just not closing connections, after a user disconnects from my
> app and i give him his 2 connections(1read/1write) back, when he
> connects again to my app.

How long your connection lives? Note, it is very sensitive part of
the JDBC. According to the specification, open connection always have
a transaction associated with it. Long transactions are usually a bad
idea, because the eat server resources. Also it is very bad idea to
have long transaction in case of Firebird, because this has an impact
on record version handling.

What is the requirement to give the same connection over and over
again to the client and keep it open?

And one more question. Can it be that you run out of socket
connections that your JVM can handle? How many open connections do
you have when JVM crashes?

> Before some selects i create new connections (and close them after
> select), because if i use old connection i sometimes get false
> results. (another bug in jaybird, i've never seen this behavior
> with interclient).

What does "false result" means here? Can it be connected with
transaction isolation?

Best regards,
Roman Rokytskyy