From derby-user-return-11698-apmail-db-derby-user-archive=db.apache.org@db.apache.org Tue Sep 29 04:42:26 2009 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 25672 invoked from network); 29 Sep 2009 04:42:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Sep 2009 04:42:26 -0000 Received: (qmail 19511 invoked by uid 500); 29 Sep 2009 04:42:25 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 19451 invoked by uid 500); 29 Sep 2009 04:42:25 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 19443 invoked by uid 99); 29 Sep 2009 04:42:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2009 04:42:25 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of matt.doran@papercut.com designates 209.68.5.15 as permitted sender) Received: from [209.68.5.15] (HELO relay01.pair.com) (209.68.5.15) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 29 Sep 2009 04:42:15 +0000 Received: (qmail 20905 invoked from network); 29 Sep 2009 04:41:52 -0000 Received: from 218.214.136.161 (HELO ?192.168.1.26?) (218.214.136.161) by relay01.pair.com with SMTP; 29 Sep 2009 04:41:52 -0000 X-pair-Authenticated: 218.214.136.161 Message-ID: <4AC1900E.7080808@papercut.com> Date: Tue, 29 Sep 2009 14:41:50 +1000 From: Matt Doran User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Derby Discussion Subject: Re: Pooling References: <4d2670740909272209k1567bf53s3eb96de862525fd7@mail.gmail.com> <4AC04C81.3090605@papercut.com> <4AC0AF1B.40001@Sun.COM> In-Reply-To: <4AC0AF1B.40001@Sun.COM> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org 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. . > > 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,