In the JDBC Connection Pool—>Configuration—>Connections tab, you specify the number of connections in the connection pool and details for each connection in the connection pool.

A connection pool contains a group of JDBC connections that are created when the connection pool is registered, usually when starting up WebLogic Server. Your application borrows a connection from the connection pool, uses it, then returns it to the connection pool by closing it.

Attribute Label	Description	Value Constraints
Initial Capacity	The number of physical database connections to create when creating the connection pool. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: InitialCapacity	Minimum: 0 Maximum: 2147483647 Default: 1 Configurable: yes Readable: yes Writable: yes
Maximum Capacity	Maximum number of physical database connections that this connection pool can contain. Different JDBC Drivers and database servers may limit the number of possible physical connections. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: MaxCapacity	Minimum: 1 Maximum: 2147483647 Default: 1 Configurable: yes Readable: yes Writable: yes
Capacity Increment	Increment by which the connection pool capacity is expanded. When there are no more available physical connections to service requests, the connection pool will create this number of additional physical database connections and add them to the connection pool. The connection pool will ensure that it does not exceed the maximum number of physical connections as set by MaxCapacity. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: CapacityIncrement	Minimum: 1 Maximum: 2147483647 Default: 1 Configurable: yes Readable: yes Writable: yes
Login Delay Seconds	The number of seconds to delay before creating each physical database connection. This delay takes place both during initial pool creation and during the lifetime of the pool whenever a physical database connection is created. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: LoginDelaySeconds	Units: seconds Minimum: 0 Maximum: 2147483647 Default: 0 Configurable: yes Readable: yes Writable: yes
Refresh Period	The number of minutes between database connection tests. After every RefreshMinutes interval, unused database connections are tested using TestTableName. Connections that do not pass the test will be closed and reopened to re-establish a valid physical database connection. If TestTableNameis not set, the test will not be performed. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: RefreshMinutes	Units: minutes Minimum: 0 Maximum: 35791394 Default: 0 Configurable: yes Readable: yes Writable: yes
Supports Local Transaction	Set to true if the XA driver used to create physical database connections supports SQL without global transactions. Set to false (the default) if the XA driver does not support SQL without global transactions. This property applies to connection pools that use an XA driver only, and is ignored for connection pools that use non-XA drivers. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: SupportsLocalTransaction	Default: false Configurable: yes Readable: yes Writable: yes
Allow Shrinking	Indicates whether or not the pool can shrink back to its InitialCapacitywhen it is detected that connections created during increased traffic are not being used. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: ShrinkingEnabled	Default: true Readable: yes Writable: yes
Shrink Period	Number of minutes to wait before shrinking a connection pool that has incrementally increased to meet demand. ShrinkingEnabledmust be set to true for a connection pool to shrink. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: ShrinkPeriodMinutes	Units: minutes Minimum: 1 Maximum: 2147483647 Default: 15 Configurable: yes Readable: yes Writable: yes
Prepared Statement Cache Size	The maximum number of prepared statements stored in the cache for further use. WebLogic Server can reuse prepared statements in the cache without reloading them, which can increase server performance. Setting the size of the prepared statement cache to 0 (the default) turns it off. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: PreparedStatementCacheSize	Default: 5 Readable: yes Writable: yes
XA Prepared Statement Cache Size	The maximum number of prepared statements stored in the cache for each connection in the connection pool for reuse. WebLogic Server can reuse prepared statements in the cache without reloading them, which can increase server performance. Setting the size of the prepared statement cache to 0 (the default) turns it off. Statements are cached and replaced in the cache according to an LRU (least recently used) algorithm. This attribute applies to connection pools that use an XA JDBC driver only. It is ignored if the connection pool uses a non-XA JDBC driver to create database connections. MBean: weblogic.management. configuration. JDBCConnectionPoolMBean Attribute: XAPreparedStatementCacheSize	Default: 0 Readable: yes Writable: yes

Attribute Label

Description

Value Constraints

Initial Capacity

The number of physical database connections to create when creating the connection pool.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: InitialCapacity

Minimum: 0

Maximum: 2147483647

Default: 1

Configurable: yes

Readable: yes

Writable: yes

Maximum Capacity

Maximum number of physical database connections that this connection pool can contain. Different JDBC Drivers and database servers may limit the number of possible physical connections.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: MaxCapacity

Minimum: 1

Maximum: 2147483647

Default: 1

Configurable: yes

Readable: yes

Writable: yes

Capacity Increment

Increment by which the connection pool capacity is expanded. When there are no more available physical connections to service requests, the connection pool will create this number of additional physical database connections and add them to the connection pool. The connection pool will ensure that it does not exceed the maximum number of physical connections as set by MaxCapacity.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: CapacityIncrement

Minimum: 1

Maximum: 2147483647

Default: 1

Configurable: yes

Readable: yes

Writable: yes

The number of seconds to delay before creating each physical database connection. This delay takes place both during initial pool creation and during the lifetime of the pool whenever a physical database connection is created.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: LoginDelaySeconds

Units: seconds

Minimum: 0

Maximum: 2147483647

Default: 0

Configurable: yes

Readable: yes

Writable: yes

Refresh Period

The number of minutes between database connection tests. After every RefreshMinutes interval, unused database connections are tested using TestTableName. Connections that do not pass the test will be closed and reopened to re-establish a valid physical database connection. If TestTableNameis not set, the test will not be performed.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: RefreshMinutes

Units: minutes

Minimum: 0

Maximum: 35791394

Default: 0

Configurable: yes

Readable: yes

Writable: yes

Supports Local Transaction

Set to true if the XA driver used to create physical database connections supports SQL without global transactions. Set to false (the default) if the XA driver does not support SQL without global transactions.

This property applies to connection pools that use an XA driver only, and is ignored for connection pools that use non-XA drivers.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: SupportsLocalTransaction

Default: false

Configurable: yes

Readable: yes

Writable: yes

Allow Shrinking

Indicates whether or not the pool can shrink back to its InitialCapacitywhen it is detected that connections created during increased traffic are not being used.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: ShrinkingEnabled

Default: true

Readable: yes

Writable: yes

Shrink Period

Number of minutes to wait before shrinking a connection pool that has incrementally increased to meet demand. ShrinkingEnabledmust be set to true for a connection pool to shrink.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: ShrinkPeriodMinutes

Units: minutes

Minimum: 1

Maximum: 2147483647

Default: 15

Configurable: yes

Readable: yes

Writable: yes

Prepared Statement Cache Size

The maximum number of prepared statements stored in the cache for further use. WebLogic Server can reuse prepared statements in the cache without reloading them, which can increase server performance. Setting the size of the prepared statement cache to 0 (the default) turns it off.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: PreparedStatementCacheSize

Default: 5

Readable: yes

Writable: yes

XA Prepared Statement Cache Size

The maximum number of prepared statements stored in the cache for each connection in the connection pool for reuse. WebLogic Server can reuse prepared statements in the cache without reloading them, which can increase server performance. Setting the size of the prepared statement cache to 0 (the default) turns it off.

Statements are cached and replaced in the cache according to an LRU (least recently used) algorithm.

This attribute applies to connection pools that use an XA JDBC driver only. It is ignored if the connection pool uses a non-XA JDBC driver to create database connections.

MBean: weblogic.management.
configuration.
JDBCConnectionPoolMBean

Attribute: XAPreparedStatementCacheSize

Default: 0

Readable: yes

Writable: yes