Hmm, then I cannot reproduce, here is a test I just added to confirm this particular case: https://git-wip-us.apache.org/repos/asf?p=tomee.git;a=blob;f=container/openejb-core/src/test/java/org/apache/openejb/resource/jdbc/XAPoolTest.java;h=2ae79195002b65bc817e70afcba3a2f8a59fbf08;hb=7b7e630e0150a8cf326465726c6cb9082b35556d
(based on previous one, only different is initial size is 0 at the beginning since the datasource is created lazily with dbcp) 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:14 GMT+02:00 iannuz <[email protected]>: > I am not sure I get what you mean. You say to switch to dbcp, but the > configuration that is giving me problems is the following, where I am > already using dbcp.. what have I misunderstood? > > <Resource id="myDBXAPooled" type="DataSource"> > XaDataSource myDBXA > *DataSourceCreator dbcp* > JtaManaged true > UserName TestUser > Password TestPassword > MaxWait 2000 > ValidationQuery SELECT 1 > InitialSize 2 > MaxActive 15 > MinIdle 3 > MaxIdle 5 > MinEvictableIdleTimeMillis 25000 > TimeBetweenEvictionRunsMillis 40000 > LogAbandoned true > RemoveAbandoned true > RemoveAbandonedTimeout 20 > </Resource> > > <Resource id="myDBXA" type="XADataSource" > class-name="com.mysql.jdbc.jdbc2.optional.MysqlXADataSource"> > Url jdbc:mysql://localhost:3306/test > User TestUser > Password TestPassword > </Resource> > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/org-apache-openejb-resource-jdbc-dbcp-BasicManagedDataSource-allocating-more-than-MaxActive-connectis-tp4676508p4676554.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
