[jesper.pedersen]

It is JBJCA-1169.

However, use-strict-min should only be used when there is connection validation of the pool, hence a <validation> element present. Otherwise you could "leak" invalid connections to the application, since the pool doesn't time them out.

You are more likely looking for the decrementer policy, through the <capacity> -> <decrementer> element...

[jesper.pedersen]

You can upgrade IronJacamar to 1.1.6-SNAPSHOT to get the fix, if use-strict-min is a requirement.

[premudriy]

I'm still seeing cpu usage going to 100% after a day. Using the latest wildfly snapshot.

My data source is specified in a different way though. Here's what I have:

<subsystem xmlns="urn:jboss:domain:datasources:2.0">
    <datasources>
        <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
            <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
            <driver>h2</driver>
            <security>
                <user-name>sa</user-name>
                <password>sa</password>
            </security>
        </datasource>
        <datasource jndi-name="java:jboss/datasources/mwuDS" pool-name="mwuDS" enabled="true" use-java-context="true">
            <connection-url>jdbc:mysql://dbnode1,dbnode2,dbnode3,dbnode4/schema?useConfigs=clusterBase&amp;useUnicode=true&amp;characterEncoding=utf8</connection-url>
            <driver>mysql</driver>
            <security>
                <user-name>dbusername</user-name>
                <password>dbpassword</password>
            </security>
        </datasource>
        <drivers>
            <driver name="h2" module="com.h2database.h2">
                <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
            </driver>
            <driver name="mysql" module="com.mysql.jdbc">
                <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
            </driver>
        </drivers>
    </datasources>
</subsystem>

However, I assume if <use-strict-min/> has a proper default value, it shouldn't cause the problem since I'm not specifying it?