---

JDBC Connection Pool --> Configuration --> Connections

Tasks     Related Topics     Attributes

 

Overview

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.

 

Tasks

Creating and Configuring a JDBC Connection Pool

Deploying a JDBC Connection Pool to One or More Servers or Clusters

Cloning a JDBC Connection Pool

Monitoring Connections in a JDBC Connection Pool

 

Related Topics

Increasing Performance with the Statement Cache

Automatically Recovering Leaked Connections

Initializing Database Connections with SQL Code

Connection Testing Options

JDBC

Programming WebLogic JDBC

Third-Party Driver Configuration and Performance Requirements in Programming WebLogic JTA

 

Attributes

Attribute Label	Description	Value Constraints
Initial Capacity	The number of physical database connections to create when creating the connection pool.MBean: weblogic.management. configuration. JDBCConnectionPoolMBeanAttribute: InitialCapacity	Minimum: 0Maximum: 2147483647Default: 1Dynamic: 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. JDBCConnectionPoolMBeanAttribute: MaxCapacity	Minimum: 1Maximum: 2147483647Default: 15Dynamic: 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. JDBCConnectionPoolMBeanAttribute: CapacityIncrement	Minimum: 1Maximum: 2147483647Default: 1Dynamic: yes
Statement Cache Type	The algorithm used to maintain the statement cache: LRU - After the statementCacheSize is met, the Least Recently Used statement is removed when a new statement is used. Fixed - The first statementCacheSize number of statements is stored and stay fixed in the cache. No new statements are cached unless the cache is manually cleared. MBean: weblogic.management. configuration. JDBCConnectionPoolMBeanAttribute: StatementCacheType	Default: LRUValid values: LRU FIXED Dynamic: no
Statement Cache Size	The number of Prepared and Callable Statements stored in the cache for further use. WebLogic Server can reuse statements in the cache without reloading them, which can increase server performance. Setting the size of the statement cache to 0 turns it off. Each connection in the pool has its own cache of statements.MBean: weblogic.management. configuration. JDBCConnectionPoolMBeanAttribute: StatementCacheSize	Default: 10Dynamic: yes

 

Advanced Attributes

Attribute Label	Description	Value Constraints
Login Delay	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. JDBCConnectionPoolMBeanAttribute: LoginDelaySeconds	Units: secondsMinimum: 0Maximum: 2147483647Default: 0Dynamic: no
Remove Infected Connections Enabled	Controls whether a connection will be removed from the connection pool and recreated after an application uses the underlying vendor connection object. When set to true, the physical connection is not returned to the connection pool after the application closes the logical connection. Instead, the physical connection is closed and recreated. When set to false, when you close the logical connection, the physical connection is returned to the connection pool. If you use this setting, make sure that the database connection is suitable for reuse by other applications.Enabling this attribute will have an impact on performance as it will essentially disable the pooling of connections (as connections will be removed from the pool and replaced with new connections).MBean: weblogic.management. configuration. JDBCConnectionPoolMBeanAttribute: RemoveInfectedConnectionsEnabled	Default: trueValid values: true false Dynamic: no
Allow Shrinking	Indicates whether or no