Romain, can you elaborate more? Tx is managed by a transaction manager, what does it have to do with the pool implementation? What does DBCP has that Tomcat pool does not have? The spin lock (locking) design alone is big enough to keep DBCP away from highly concurrent web apps. Tomcat pool or BoneCP is the way to go in Tomee IMO.
Once you finish your testing, let me know I can test my project with your changes. Please be sure that it'll work with META-INF/resources.xml packaged with a project. Thanks! -- View this message in context: http://openejb.979440.n4.nabble.com/DB-pool-resource-Tomee-production-tp4656425p4656454.html Sent from the OpenEJB User mailing list archive at Nabble.com.
