When editing a JDBC Connection Pool, all settings can be revised except the name of the Connection Pool.
The Connection Pools page opens.
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.
This class is in the JDBC driver.
Choices include javax.sql.DataSource (local transactions only), javax.sql.XADataSource (global transactions), and java.sql.ConnectionPoolDataSource (local transactions, possible performance improvements).
This value also determines the number of connections placed in the pool when the pool is first created or when the Enterprise Server starts.
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.
After this time expires, the connection is removed from the pool.
Connection validation allows the server to reconnect in case of failure.
The application server can validate database connections in three ways: auto-commit, metadata, and table.
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.
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.
The table name must contain only alphanumeric, underscore, dash, or dot characters.
If this option is disabled, individual connections are re-established only when they are used.
If not specified, the connections operate with default isolation levels provided by the JDBC driver.
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.