Re: DataSource / OOM problem (was Re: Recommending 3.0.19)
"sks" <[email protected]> Tue, 20 Jun 2006 14:30:36 +0100
| Newsgroups | gmane.text.xml.resin.user |
|---|---|
| Message-ID | <002401c6946d$b83f7370$0200a8c0@sks1> |
Thanks I'll give it a blast, I seem to be having no oom problems with DBPool today so that's promising (I only started trying it last night). I've preferred c3p0 and proxool to dbcp, but I've never had serious problems with any of these. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andy Yates Sent: June 20, 2006 8:19 AM To: [email protected] Subject: Re: DataSource / OOM problem (was Re: Recommending 3.0.19) Try c3po as well if you don't like jakarta stuff (that said I've used dbcp now for 3+ yrs and I have no issues with it). Andy sks wrote: > I don't like to use jakarta stuff, but I've tried this pool with > limited success. > http://homepages.nildram.co.uk/~slink/java/DBPool/ > > >> At 2006-06-20 12:54, sks wrote: >>> Yes Scott has acknowledged it as an issue. I can get around it by >>> stopping using a datasource and getting a connection to the database >>> using the good old fashioned java.sql.DriverManager.getConnection >>> but obviously that's quite inefficient. >> >> >> Couldn't you just put a DBCP >> (http://jakarta.apache.org/commons/dbcp/) >> pool in JNDI? >> >> >> > > >