Use the New JDBC Connection Pool (Step 2 of 2) page to create a new JDBC connection pool.
The New JDBC Connection Pool (Step 2 of 2) page contains the following options.
The vendor-specific class name that implements the DataSource or XADataSource APIs.
A short description for the connection pool.
The minimum number of connections in the pool. This value also determines the number of connections placed in the pool when the pool is first created or when application server starts.
The maximum number of connections in the pool.
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.
The maximum amount of time, in seconds, that a connection can remain idle in the pool. After this time expires, the connection is removed from the pool.
The maximum amount of time, in milliseconds, that the application requesting a connection will wait before getting a connection timeout.
If this option is selected, connection validation is required, allowing 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 no rows are required. Do not use an existing table that has a large number of rows, or a table that is already frequently accessed.
Name of the database table for validation.
This field is only applicable if the validation method was set to Table in the preceding field.
If this option is enabled, the application server closes all connections in the pool and re-establishes them when any connection fails. If the option is disabled, then individual connections are re-established only when they are used.
If this option is enabled, the pool can be used by non-component callers such as servlet filters.
If this option is enabled, non-transactional connections are returned.
If a transaction isolation level is specified, connections in this pool operate at the specified level. Otherwise, the connections operate with default isolation levels provided by the JDBC driver.
This field is only applicable if a transaction isolation level was specified in the preceding field.
If the Guaranteed checkbox is selected, then 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, then this mechanism changes the status back to the specified isolation level.
Additional properties for the JDBC connection pool. These properties might include database name (URL), user name, and password.
For a description of connection pool properties, see Properties Specific to JDBC Connection Pools.