To Edit JDBC Connection Pool General Settings

When editing a JDBC Connection Pool, all settings can be revised except the name of the Connection Pool.

  1. In the navigation tree, expand the Resources node.
  2. Under the Resources node, expand the JDBC node.
  3. Under the JDBC node, select the Connection Pools node.

    The Connection Pools page opens.

  4. Click the name of the connection pool that you are editing.

    The Edit Connection Pool page opens.


    Note - The Name field is a read-only field. You can only specify the connection pool name when you create a new JDBC connection pool.


  5. In the Datasource Classname field, type the name of the vendor-specific class that implements the DataSource and/or XADataSource APIs.

    This class is in the JDBC driver.

  6. From the Resource Type drop-down list, select a resource type.

    Choices include javax.sql.DataSource (local transactions only), javax.sql.XADataSource (global transactions), and java.sql.ConnectionPoolDataSource (local transactions, possible performance improvements).

  7. In the Description field, type a short description for the connection pool.
  8. In the Initial and Minimum Pool Size field, type the minimum number of connections in this pool.

    This value also determines the number of connections placed in the pool when the pool is first created or when the Enterprise Server starts.

  9. In the Maximum Pool Size field, type the maximum number of connections in this pool.
  10. In the Pool Resize Quantity field, type the number of connections per pool resizing batch.

    When the pool scales up and scales down toward the maximum and minimum pool size respectively, it is resized in batches. This value determines the number of connections in the batch. Making this value too large delays connection creation and recycling; making it too small will be less efficient.

  11. In the Idle Timeout field, type the maximum time, in seconds, that a connection can remain idle in the pool.

    After this time expires, the connection is removed from the pool.

  12. In the Max Wait Time field, type the maximum time, in milliseconds, that an application requesting a connection will wait before getting a connection timeout.
  13. Select the Connection Validation Required checkbox to enable connection validation.

    Connection validation allows the server to reconnect in case of failure.

  14. From the Validation Method drop-down list, select a validation method.

    The application server can validate database connections in three ways: auto-commit, metadata, and table.

    Auto-commit and metadata

    The application server validates a connection by calling the con.getAutoCommit and con.getMetaData methods.


    Note - Many JDBC drivers cache the results of these calls. As a result, using these calls might not always provide reliable validations. Check with the driver vendor to determine whether these calls are cached or not.


    Table

    The application queries the database table that is specified. The table must exist and be accessible, but it doesn't require any rows. Do not use an existing table that has a large number of rows, or a table that is already frequently accessed.

  15. If you selected Table in the Validation Method drop-down list, type the name of the database table in the Table Name field.

    The table name must contain only alphanumeric, underscore, dash, or dot characters.

  16. Select the On Any Failure Close All Connections checkbox to have the server close and re-establish all connections in the pool in the event of a single connection failure.

    If this option is disabled, individual connections are re-established only when they are used.

  17. Select the Allow Non Component Callers Enabled checkbox to allow the pool to be used by non-component callers such as servlet filters.
  18. Select the Non Transactional Connections Enabled checkbox to return non-transactional connections.
  19. Select a Transaction Isolation level for the connection pool from the drop-down list.

    If not specified, the connections operate with default isolation levels provided by the JDBC driver.

  20. Select the Isolation Level Guaranteed checkbox so that all connections taken from the pool have the same isolation level.

    For example, if the isolation level for the connection is changed programmatically (with con.setTransactionIsolation) when last used, this mechanism changes the status back to the specified isolation level.

    This setting is only applicable if a transaction isolation level has been specified.

  21. Click Save.
See Also