On Sat, 22 Feb 2014 16:33:07 +0100, Mark Rotteveel <mark@...>
wrote:

> On Sat, 22 Feb 2014 13:49:16 +0000, "Steffen Heil (Mailinglisten)"
> <lists@...> wrote:
>> Hi
>>
>> Using FBWrappingDataSource we encountered problems (after years without
>> problems).
>> We suspect a bug in PooledConnectionQueue, but we are not sure.
>>
>> I just created a bug report.
>>
>> http://tracker.firebirdsql.org/browse/JDBC-341
>>
>> Any hints are welcome.
>
> For Jaybird 2.2 I fixed some concurrency bugs in this class, but due to
> other fundamental flaws in the implementation of the connection pool in

the

> org.firebirdsql.pool classes, I have decided to deprecate the entire
> package (see
>

http://www.firebirdsql.org/file/documentation/drivers_documentation/java/2.2.4/release_notes.html#__RefHeading__2753_1560579136

> and
>

http://www.firebirdsql.org/file/documentation/drivers_documentation/java/2.2.4/release_notes.html#__RefHeading__2807_1560579136).

> In Jaybird 3.0 this entire package is going to be removed entirely.
>
> Although I thought FBWrappingDataSource worked correctly with the
> deprecated implementations, that - as demonstrated by your issue - might
> not be the case. However as this whole package will be removed I will

not

> investigate in detail, but only amend the releasenotes for 2.2.5. I

suggest

> you either move to a third party connection pool (c3p0, BoneCP or DBCP)

or

> use the connection pool provided by your application server (if this is

run

> in an application server).

I have thought this over during the weekend, and I will be investigating
the bug. If I can identify the cause and the fix doesn't have too much
impact, I will fix it in Jaybird 2.2.5 or 2.2.6.

However my advice remains: switch to a third party connection pool (or use
the one built-in in your application server).

Mark