<<
We are using a home made connection pool, and are experiencing what seems to
be the same problem.

But we are NOT using the build in pool (FBWrappingDataSource).

Of course I am not completely sure if our code is correct, but we have tried
to find the error for some time and we just can´t.

>>

Indeed, we also had the problem when using the connection broker from javaexchange.com. The problem seems to be located on a lower level than in the connection broker.

<<
Previous we "recycled" the connections every 15 minutes and got the error
aprox. once a week.

Now we only recycle every 6 hours, and until now have not had the error in 1
month.

>>

We've set the idle timeout to an hour as a temporary workaround.

<<
Ps: Except for this "small" problem, we are VERY satisfied with the driver.
You guys are doing a great job :-)

>>

Couldn't agree more! We've had very little problems switching over to this driver and are really satisfied performance-wise.

Natal Vande Casteele