JBoss Community

Re: possible bad side effects from change to AbstractConnectionManager

created by Marc Rosenthal in IronJacamar Development - View the full discussion

I had the same issue with the latest jboss snapshot: jboss-as-7.2.0.Alpha1-SNAPSHOT

 

The trace is here.

 

My datasource config:

 

                <datasource jta="true" jndi-name="java:jboss/datasources/atDS" pool-name="MySqlDS" enabled="true" spy="true" use-ccm="true">

                    <connection-url>jdbc:mysql://dbserv:3306/db</connection-url>

                    <driver-class>com.mysql.jdbc.Driver</driver-class>

                    <driver>mysql-connector-java-5.1.22-bin.jar</driver>

                    <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>

                    <pool>

                        <min-pool-size>0</min-pool-size>

                        <max-pool-size>1</max-pool-size>

                        <prefill>true</prefill>

                        <use-strict-min>true</use-strict-min>

                        <flush-strategy>IdleConnections</flush-strategy>

                    </pool>

                    <security>

                        <user-name>user</user-name>

                        <password>passwd</password>

                    </security>

                    <validation>

                        <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>

                        <stale-connection-checker class-name="org.jboss.jca.adatpers.jdbc.extensions.mysql.MySQLStaleConnectionChecker"/>

                        <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>

                    </validation>

                    <timeout>

                        <allocation-retry>3</allocation-retry>

                    </timeout>

                </datasource>

Reply to this message by going to Community

Start a new discussion in IronJacamar Development at Community