Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-6624

Jboss connection pool is not auto reconnects to mySQl (XA-datasource)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 7.1.1.Final
    • JCA
    • None

      I am using JPA Hibernate in Timer EJB.
      After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened.
      my datasource is

      <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true">
      <xa-datasource-property name="ServerName">
      localhost
      </xa-datasource-property>
      <xa-datasource-property name="DatabaseName">
      db
      </xa-datasource-property>
      <xa-datasource-property name="User">
      root
      </xa-datasource-property>
      <xa-datasource-property name="Password">
      xxxxx
      </xa-datasource-property>
      <xa-datasource-property name="AutoReconnectForPools">
      true
      </xa-datasource-property>
      <xa-datasource-property name="FailOverReadOnly">
      false
      </xa-datasource-property>
      <xa-datasource-property name="MaxReconnects">
      100
      </xa-datasource-property>
      <xa-datasource-property name="ReconnectAtTxEnd">
      true
      </xa-datasource-property>
      <driver>com.mysql</driver>
      <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
      <validation>
      <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
      <check-valid-connection-sql>select 1</check-valid-connection-sql>
      <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
      </validation>
      </xa-datasource>

              smaestri@redhat.com Stefano Maestri
              als_jira Alexey S. (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: