Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Verify Connection Pool Settings in server.properties

    Hi

    I have the following code in my server.properties file
    Code:
    sql.Oracle.driver: oracle.jdbc.pool.OracleDataSource
    sql.Oracle.pool.maxActive:10
    sql.Oracle.pool.maxIdle:5
    sql.Oracle.pool.maxWait:5000
    sql.Oracle.pool.minEvictableIdleTimeMillis:5000
    sql.Oracle.pool.numTestsPerEvictionRun: 5
    sql.Oracle.pool.timeBetweenEvictionRunsMillis: 10000
    How can I verify that these connection pooling properties are actually being set?

    #2
    One approach would be to use Oracle tools or network monitors to see how many connections are being created.

    Comment


      #3
      Hello

      I have a similar question - not sure if the pooling really works (my yourkit profiling shows too many getPhysicalConnection() calls than what am expecting).

      Obviously am missing something, but can help figure out what it is?

      Here's how my server.properties looks

      sql.defaultDatabase: Oracle

      sql.Oracle.database.type: oracle
      sql.Oracle.interface.type: dataSource
      sql.Oracle.driver.serverName = *.*.*.*
      sql.Oracle.driver.portNumber: 1521
      sql.Oracle.driver.databaseName: FSE
      sql.Oracle.driver: oracle.jdbc.pool.OracleDataSource
      sql.Oracle.pool.maxActive:10
      sql.Oracle.pool.maxIdle:2
      sql.Oracle.pool.maxWait:5000
      sql.Oracle.pool.minEvictableIdleTimeMillis:5000
      sql.Oracle.pool.numTestsPerEvictionRun: 5
      sql.Oracle.pool.timeBetweenEvictionRunsMillis: 10000
      sql.Oracle.pool.enabled: true
      sql.Oracle.autoJoinTransactions: true
      sql.Oracle.driver.type: thin
      sql.oracle.supportsSQLLimit: false
      sql.Oracle.driver.user: ****
      sql.Oracle.driver.password: ******

      <DataSource
      dbName="Oracle"
      tableName="T_CATALOG"
      ID="T_CATALOG_DEMAND"
      serverType="sql"

      Regards
      Rajesh
      Last edited by rpatibandla; 16th Nov 2012, 09:27.

      Comment


        #4
        Not sure where you got those settings, but they appear scrambled (things being set on the wrong objects). We would recommend deleting all these settings and using the defaults (which work).

        Comment


          #5
          Thanks for the reply. Much appreciated. You mean get rid of all pool related properties? And you mean pooling is enabled by default? If so, what are the default pooling characteristics (grow when exhausted etc)?

          Apologies for the naivity - but i dont think there this is documented in detail, or atleast am looking at wrong place.

          Let me know

          Comment


            #6
            We use Apache DBCP and we leave the defaults alone except to turn off eviction runs, which are known to cause deadlocks in DBCP prior to 1.2.2 (and we haven't verified the claim fix for 1.2.2).

            Comment


              #7
              Hi Warren.Menezes,

              Originally posted by Warren.Menezes View Post
              How can I verify that these connection pooling properties are actually being set?
              pretty old thread, but perhaps (did not try) this is also possible via JMX.

              Best regards
              Blama

              Comment

              Working...
              X