Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 42565 invoked from network); 20 Jan 2009 13:37:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Jan 2009 13:37:40 -0000 Received: (qmail 32209 invoked by uid 500); 20 Jan 2009 13:37:37 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 32198 invoked by uid 500); 20 Jan 2009 13:37:37 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 32189 invoked by uid 99); 20 Jan 2009 13:37:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2009 05:37:37 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of clinton.begin@gmail.com designates 209.85.146.183 as permitted sender) Received: from [209.85.146.183] (HELO wa-out-1112.google.com) (209.85.146.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2009 13:37:30 +0000 Received: by wa-out-1112.google.com with SMTP id m28so601983wag.0 for ; Tue, 20 Jan 2009 05:37:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=wsDdGHMSJEbnxJ9RJhTA5xAWcljqDvSluOvknX47H3U=; b=Isj/4YnPUFy5AKzuIbs04kxdiQUFRJTOVWKc6XCD81u2ZOUZPwcDnZwO2qhVgeo6Zr GpynQTaxuGRwS+NfJffhmbKdU2nKJPI64EoaFol9LwHztgy54dd50UUOSyo3G4RnACvh YvTUxz9YJc0NK3Z7Jo3WCVLUFfd6iUNchcuC8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=jOGuiwBhjSndhos/kmJd3KtbI51NU/C2sSyxL1fx44s7GYjn637MLUKQU1TME8+gxy nSXEc+dj6JjaUYprfxHqHWZrbpezTx83qFquuY2kjqNsbcJLpXtpmc/mbXt6jpPbphU6 4gRg0ypV8zCUG8hrr63fZ2kZNxyvmLUkA0bJw= MIME-Version: 1.0 Received: by 10.114.208.20 with SMTP id f20mr2732131wag.46.1232458630285; Tue, 20 Jan 2009 05:37:10 -0800 (PST) In-Reply-To: <583d4dff0901190745q22344643ma39d275f3b84e5c7@mail.gmail.com> References: <49738175.2090206@intland.com> <583d4dff0901190745q22344643ma39d275f3b84e5c7@mail.gmail.com> Date: Tue, 20 Jan 2009 06:37:10 -0700 Message-ID: <16178eb10901200537o66304357oc47ff649b6589fc0@mail.gmail.com> Subject: Re: ibatis db pool or dbcp From: Clinton Begin To: user-java@ibatis.apache.org Content-Type: multipart/alternative; boundary=00163646d97fdbc8b60460ea22c2 X-Virus-Checked: Checked by ClamAV on apache.org --00163646d97fdbc8b60460ea22c2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Yes, they're both fine for production. iBATIS SimpleDataSource has been around since iBATIS 1.0 and has changed very little (but it does get a major facelift in iBATIS 3.0). The difference between the iBATIS SimpleDataSource and most others is that it's a synchronous datasource. That is, it does not spawn reaper threads or manage the pool with anything other than the current thread. Overdue, stale or invalid connections are dealt with at the point of request. For some this is an advantage, for others, it's not. IMHO, the fewer threads the better... the work has to happen somewhere, so why not the current thread? :-) Cheers, Clinton On Mon, Jan 19, 2009 at 8:45 AM, Rick wrote: > On Sun, Jan 18, 2009 at 2:22 PM, Zsolt Koppany > wrote: > > Hi, > > > > which database pool is recommended for production usage? The pool shipped > > with ibatis or dbcp? > > > > We use ibatis 2.3.4.726. > > I'm curious about this also. I heard the ibatis common pool is fine > for production. Are you better off using dbcp or one that is provided > by a container?- I don't really know, and would be interested on > thoughts by those that know a heck of a lot more about it than me. > --00163646d97fdbc8b60460ea22c2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes, they're both fine for production.  iBATIS SimpleDataSource ha= s been around since iBATIS 1.0 and has changed very little (but it does get= a major facelift in iBATIS 3.0).  The difference between the iBATIS S= impleDataSource and most others is that it's a synchronous datasource.&= nbsp; That is, it does not spawn reaper threads or manage the pool with any= thing other than the current thread.  Overdue, stale or invalid connec= tions are dealt with at the point of request.  For some this is an adv= antage, for others, it's not.  IMHO, the fewer threads the better.= .. the work has to happen somewhere, so why not the current thread?  := -)

Cheers,
Clinton

On Mon, Jan 19, 20= 09 at 8:45 AM, Rick <rickcr@gmail.com> wrote:
On Sun, Jan 18, 2009 at 2:22 PM, Zsol= t Koppany <zkoppanylist@intl= and.com> wrote:
> Hi,
>
> which database pool is recommended for production usage? The pool ship= ped
> with ibatis or dbcp?
>
> We use ibatis 2.3.4.726.

I'm curious about this also. I heard the ibatis common pool= is fine
for production. Are you better off using dbcp or one that is provided
by a container?- I don't really know, and would be interested on
thoughts by those that know a heck of a lot more about it than me.

--00163646d97fdbc8b60460ea22c2--