Hmm if you have MaxIdle < MaxActive (or MaxTotal - has been renamed for dbcp 2) what is your expectation because it means you can't get enough datasources (actives ones are taken from idle ones - even if idle duration can be 0ms if immediately required).
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-10-22 13:46 GMT+02:00 iannuz <[email protected]>: > I am not sure if what you have in your test case: > 77 .p("xadb.MaxIdle", "25") > 78 .p("xadb.MaxTotal", "25") > 79 .p("xadb.InitialSize", "3") > > corresponds to these values in my datasource definition in tomee.xml: > MaxIdle = 25 > MaxActive = 25 > InitialSize =3 > > If so you should have MaxIdle < MaxActive to see the bad behavior I see > (when many threads compete concurrently to get connections). > I also see that the test case uses "jdbc:hsqldb:mem:dbcpxa" and not MySql > XA > Driver. > > In any case I will try to package my test app as you require and share it > asap. > At the moment it is just an Eclipse Web App (no maven). > > Thanks for now :) > > m. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/org-apache-openejb-resource-jdbc-dbcp-BasicManagedDataSource-allocating-more-than-MaxActive-connectis-tp4676508p4676556.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
