1 Reply Latest reply on May 24, 2013 8:55 AM by Jesper Pedersen

    Datasource pool config

    Frank Langelage Master

      I'm using WildFly 8.0.0.Alpha2-SNAPSHOT build from current sources.

       

      My oracle datasource is configured via external ds.xml file like this:

      {code:xml}

      <?xml version="1.0" encoding="UTF-8"?>

      <datasources xmlns="http://www.jboss.org/ironjacamar/schema">

        <datasource jndi-name="dbname" enabled="true" use-java-context="true" pool-name="dbname">

          <connection-url>jdbc:oracle:thin:@host:1521:DEV</connection-url>

          <driver>ojdbc6.jar</driver>

          <security>

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

            <password>password</password>

          </security>

          <validation>

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

            <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>

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

          </validation>

          <statement>

            <prepared-statement-cache-size>100</prepared-statement-cache-size>

          </statement>

        </datasource>

      </datasources>

      {code:xml}

       

      Currently the pool has 15 entries meaning 15 established connections to the oracle server.

      Only one thread is active deleting some data, delete is done with a business method annotated with REQUIRES_NEW.

      It seems, that the sessions are used round robin, because all 15 oracle processes are slowly consuming CPU time.

      And because all are used constantly, no one times out and is ended.

       

      Is there a chance to configure that WildFly uses one connection so that the others can ime out and the number of database connects will decrease?