Use the Edit Connection Pool page to edit the general properties of a JDBC connection pool.
The Edit Connection Pool page contains the following options.
The name of the connection pool. This is a read-only field. You can only specify the name when you create a JDBC connection pool.
Choices include javax.sql.XADataSource (global transactions), java.sql.ConnectionPoolDataSource (local transactions, possible performance improvements), and javax.sql.DataSource (local transactions only).
The vendor-specific class name that implements the data source.
The vendor-supplied JDBC driver class name. This driver must implement the java.sql.Driver interface. The driver classname is a read-only field.
If this option is selected, the pool will be pinged automatically during pool creation or reconfiguration to identify and warn of any erroneous attribute values. This option is disabled by default.
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 the Enterprise Server starts. The default value is 8.
The maximum number of connections in the pool. The default value is 32.
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 default value is 2.
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. The default value is 300.
The maximum time, in milliseconds, that an application requesting a connection will wait before getting a connection timeout. The default value is 60,000.
If this option is enabled, non-transactional connections are returned. By default, this option is not specified.
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. By default, this option is not specified.
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.
This field is only applicable if a transaction isolation level has been specified.