db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Doran <matt.do...@papercut.com>
Subject Re: Pooling
Date Tue, 29 Sep 2009 04:41:50 GMT
Kristian Waagan wrote:
> Matt Doran wrote:
>> Peter Ondruška wrote:
>>> Yes, Derby does not provide connection pool, pick your favourite (I 
>>> can confirm c3p0 works very well for me). Peter
>>>
>> We also use c3p0 with embedded derby, but it's mainly just our 
>> default configuration so if you switch our app over to a network 
>> based database you can take advantage of the pooling.
>>
>> When using embedded derby is there advantage (or disadvantage!) to 
>> using a DB connection pool?
>
> Hi Matt,
>
> I see some people claim c3p0 is a "dead project". Does anyone know if 
> this is the fact?
> From the SourceForge site I see that the last download was added in 
> May 2007. Even though there hasn't been any releases lately, the 
> project may still be of great use to people :)
I'm not sure.  But it's still shipped with the latest version of 
Hibernate ... so that's a pretty good indication that it's a pretty good 
utility.  And we've never had any problem with it and we have 10,000's 
of customer using our product.   <shrug>.

>
> I also remember that some people had problems using a certain c3p0 
> version with Derby embedded because c3p0 used Thread.interrupt(). This 
> caused Derby to abort writes (at least when using NIO). With the 
> client driver, this isn't a problem.
> I'm not sure if this problem is present in the latest version of c3p0 
> (maybe one could do a quick scan of the source).
>
>
> Regards,

Mime
View raw message