for a low
> >> Level connection pool. on the other hand i always wished for jdbc pools
> >> with no fixed direct relation between logical and managed connection
> >> objects.
> >>
> >> --
> >> http://bernd.eckenfels.net
> >>
> >> - Ursprünglich
nt for
>> instance and extensibility.
>> Probably there are orher data access libraries like this as well.
>>
>> Regards,
>>
>> Woonsan
>> (Sent via my mobile device. Apologies for any typos.)
>>
>> Original message From: Kasper Sø
; http://bernd.eckenfels.net
>
> - Ursprüngliche Nachricht -
> Von: "woon_san"
> Gesendet: 25.09.2014 01:38
> An: "Commons Developers List"
> Betreff: RE: A reactive way to deal with stale connections
>
> Hi Kasper,
>
> It's an inter
: "Commons Developers List"
Betreff: RE: A reactive way to deal with stale connections
Hi Kasper,
It's an interesting feature, but I don't think that should belong to
commons-dbcp. Commons-dbcp module provides lower level JDBC api such as
DataSource and Connection, whereas yo
orher data access libraries like this as well.
Regards,
Woonsan
(Sent via my mobile device. Apologies for any typos.)
Original message From: Kasper Sørensen
Date:09/24/2014 13:44 (GMT-05:00)
To: dev@commons.apache.org Subject: A reactive way to
deal with stale connections
Hi
Hi,
In many projects I have been working on we're using commons-dbcp, and in
particular the BasicDataSource. A common set-up there is to use
"testOnBorrow" and a validation query to ensure that borrowed JDBC
connections are working when we get them.
The downside of this approach is that it's pret