PS: If you're using an application server, my recommendation is to use the container managed DataSource... always always always...
Cheers, Clinton On Tue, Jan 20, 2009 at 6:37 AM, Clinton Begin <clinton.be...@gmail.com>wrote: > 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 <ric...@gmail.com> wrote: > >> On Sun, Jan 18, 2009 at 2:22 PM, Zsolt Koppany <zkoppanyl...@intland.com> >> 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. >> > >
