It's a good plan, at least BoneCP offers what Tomcat pool offers, JTA compatible, and web apps like mine would not mind adding the new jar and deleting 2 jars needed by DBCP and commons pool. BoneCP has good design for concurrency and abandoned connections, which is lacking in DBCP.
I'll be happy with this BoneCP option if it works reliably, and can be packaged in resources.xml. Thanks for the good work, you guys are awesome! -- View this message in context: http://openejb.979440.n4.nabble.com/Dbcp-and-tomee-tp4656450p4656520.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
