*>*What problems did you have with DBCP?* *I reported them here recently in post named 'Prepared Statement caching', let me just repeat
DBCP realization of poolPreparedStatements seems to contain bug. We observed that in a rare cases under heavy load some statements in a single transaction (procedure calls and select statements) were executed on different physical connections (monitored using database tracelog). We had no time to dig deeper, but now when we disabled statement caching the problem has gone, Let me add that everything runs OK with iBatis pool.
