Serge, I'm using DBCP in a production environment. It actually does support validation queries to detect whether a connection is bogus or not.
You just need to call setValidationQuery() on the PoolableConnectionFactory, and enable testOnBorrow on the ObjectPool you pass to the DBCP init stuff. I can provide sample code if you'd like. But like David said earlier, DBCP is pretty much a dead project. It works well enough for my needs, but I'm not sure I'd integrate it into a project right now. On a related note, does anybody know what the status of PreparedStatement pooling is in the latest DBCP release? It seems broken to me, but I might be doing something wrong. -- Mark Lewis On Sun, 2003-06-22 at 19:06, Serge Knystautas wrote: > Is anyone working on DBCP or planning another release anytime soon? > It's been almost a year, and the project seems pretty inactive. > > I was trying to integrate DBCP into James this weekend to replace my > home-rolled DB connection, and after the fact realized that DBCP cannot > handle database restarts as without a validate SQL statement, DBCP > doesn't realize connections are corrupt and keeps putting them back in > the pool. > > Would anyone be interested in me supplying some patches to do some extra > checking, get some examples and documentation straight (I found 3 or 4 > different "basic" examples, none of which worked for me)? Are other > Apache projects using DBCP at this point, and is it reasonable to remove > methods that have not been implemented (like setLoginTimeout())? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
