Application-Scoped JDBC Connection Pools --> Configuration --> Descriptors

Application-Scoped JDBC Connection Pools --> Configuration --> Descriptors

Tasks Related Topics Attributes

Overview

If you deployed your application as an exploded archive, you can view and edit application-scoped connection pool attributes on the Descriptors tab. If you deployed your application as an archived file, you cannot view or change attributes on this page.

Tasks

Configuring Application-Scoped Connection Pool Attributes

Related Topics

Application-Scoped JDBC Data Sources and Connection Pools
Deploying Applications and Modules
Configuring JDBC Connection Pools

Attributes

Attribute Label

Description

Value Constraints
Initial Capacity The number of physical database connections to create when creating the connection pool. Minimum: 0Maximum: 2147483647Default: 1Dynamic: yes
Max 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. 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. Minimum: 1Maximum: 2147483647Default: 1Dynamic: yes
Shrinking Enabled Indicates whether or not the pool can shrink back to its InitialCapacity when it is detected that connections created during increased traffic are not being used. When shrinking, the number of connections is reduced to the greater of either the initial capacity or the current number of connections in use. Default: trueValid values:
true

false
Dynamic: yes
Shrink Frequency Seconds Number of seconds to wait before shrinking a connection pool that has incrementally increased to meet demand. ShrinkingEnabled must be set to true for a connection pool to shrink. Units: secondsMinimum: 0Maximum: 2147483647Default: 900Dynamic: yes
Highest Num Unavailable The maximum number of connections in the pool that can be made unavailable (to an application) for purposes like refreshing the connection, etc. Note that in cases like the backend system being unavailable, this specified value could be exceeded due to factors outside the pool's control. When set to 0 (the default), this feature is disabled. Minimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Highest Num Waiters The maximum number of connection requests that can concurrently block waiting to reserve a connection from the pool. Minimum: 0Maximum: 2147483647Default: 2147483647Dynamic: yes
Check On Create Enabled When selected (set to true), WebLogic Server tests a connection after creating it and before adding it to the list of connections available to the application. The test adds a small delay in creating the connection, but ensures that the application receives a working connection. TableName must be specified. Default: falseValid values:
true

false
Dynamic: yes
Check On Reserve Enabled When selected (set to true), WebLogic Server tests a connection before giving it to the application. The test adds a small delay in serving the request for a connection from the pool, but ensures that the application receives a working connection. TableName must be set. Default: falseValid values:
true

false
Dynamic: yes
Check On Release Enabled When selected (set to true), WebLogic Server tests a connection before returning it to the connection pool. If all connections in the pool are already in use and a client is waiting for a connection, the client's wait will be slightly longer while the connection is tested. The attribute TableName must be set for Check On Release to be effective. Default: falseValid values:
true

false
Dynamic: yes
Inactive Connection Timeout Seconds The number of seconds of inactivity after which reserved connections will forcibly be released back into the pool. When set to 0 (the default), this feature is disabled. Units: secondsMinimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Connection Reserve Timeout Seconds The number of seconds after which a call to reserve a connection from the pool will timeout. When set to -1, a call will never timeout. Units: secondsMinimum: -1Maximum: 2147483647Default: 10Dynamic: yes
Test Frequency Seconds The number of seconds between database connection tests. After every TestFrequencySeconds interval, unused database connections are tested using TableName. Connections that do not pass the test will be closed and reopened to re-establish a valid physical database connection. If the test fails again, the connection is closed. If TableName is not set, the test will not be performed. If set to 0 (the default), connections are not tested. Units: secondsMinimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Connection Creation Retry Frequency Seconds The frequency of retry attempts by the pool to establish connections to the database. When set to 0 (the default), this feature is disabled. Units: secondsMinimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Table Name The name of the table used when testing a physical database connection. The default SQL code used to test a connection is select count(*) from TableName" The TableName must exist and be accessible to the database user for the connection. Most database servers optimize this SQL to avoid a table scan, but it is still a good idea to set TableName to the name of a table that is known to have few rows, or even no rows. If TableName begins with "SQL ", then the rest of the string following that leading token will be taken as a literal SQL statement that will be used to test a connection.

Init SQL The SQL code used to initialize a connection. If you specify a value for Init SQL, WebLogic Server will run the query when it creates a database connection. If no value is set for Init SQL, WebLogic Server does not run any SQL code to initialize the connection.Start the code with SQL followed by a space.

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. Default: 10Dynamic: yes

Attribute Label	Description	Value Constraints
Initial Capacity	The number of physical database connections to create when creating the connection pool.	Minimum: 0Maximum: 2147483647Default: 1Dynamic: yes
Max 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.	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.	Minimum: 1Maximum: 2147483647Default: 1Dynamic: yes
Shrinking Enabled	Indicates whether or not the pool can shrink back to its InitialCapacity when it is detected that connections created during increased traffic are not being used. When shrinking, the number of connections is reduced to the greater of either the initial capacity or the current number of connections in use.	Default: trueValid values: true false Dynamic: yes
Shrink Frequency Seconds	Number of seconds to wait before shrinking a connection pool that has incrementally increased to meet demand. ShrinkingEnabled must be set to true for a connection pool to shrink.	Units: secondsMinimum: 0Maximum: 2147483647Default: 900Dynamic: yes
Highest Num Unavailable	The maximum number of connections in the pool that can be made unavailable (to an application) for purposes like refreshing the connection, etc. Note that in cases like the backend system being unavailable, this specified value could be exceeded due to factors outside the pool's control. When set to 0 (the default), this feature is disabled.	Minimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Highest Num Waiters	The maximum number of connection requests that can concurrently block waiting to reserve a connection from the pool.	Minimum: 0Maximum: 2147483647Default: 2147483647Dynamic: yes
Check On Create Enabled	When selected (set to true), WebLogic Server tests a connection after creating it and before adding it to the list of connections available to the application. The test adds a small delay in creating the connection, but ensures that the application receives a working connection. TableName must be specified.	Default: falseValid values: true false Dynamic: yes
Check On Reserve Enabled	When selected (set to true), WebLogic Server tests a connection before giving it to the application. The test adds a small delay in serving the request for a connection from the pool, but ensures that the application receives a working connection. TableName must be set.	Default: falseValid values: true false Dynamic: yes
Check On Release Enabled	When selected (set to true), WebLogic Server tests a connection before returning it to the connection pool. If all connections in the pool are already in use and a client is waiting for a connection, the client's wait will be slightly longer while the connection is tested. The attribute TableName must be set for Check On Release to be effective.	Default: falseValid values: true false Dynamic: yes
Inactive Connection Timeout Seconds	The number of seconds of inactivity after which reserved connections will forcibly be released back into the pool. When set to 0 (the default), this feature is disabled.	Units: secondsMinimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Connection Reserve Timeout Seconds	The number of seconds after which a call to reserve a connection from the pool will timeout. When set to -1, a call will never timeout.	Units: secondsMinimum: -1Maximum: 2147483647Default: 10Dynamic: yes
Test Frequency Seconds	The number of seconds between database connection tests. After every TestFrequencySeconds interval, unused database connections are tested using TableName. Connections that do not pass the test will be closed and reopened to re-establish a valid physical database connection. If the test fails again, the connection is closed. If TableName is not set, the test will not be performed. If set to 0 (the default), connections are not tested.	Units: secondsMinimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Connection Creation Retry Frequency Seconds	The frequency of retry attempts by the pool to establish connections to the database. When set to 0 (the default), this feature is disabled.	Units: secondsMinimum: 0Maximum: 2147483647Default: 0Dynamic: yes
Table Name	The name of the table used when testing a physical database connection. The default SQL code used to test a connection is select count(*) from TableName" The TableName must exist and be accessible to the database user for the connection. Most database servers optimize this SQL to avoid a table scan, but it is still a good idea to set TableName to the name of a table that is known to have few rows, or even no rows. If TableName begins with "SQL ", then the rest of the string following that leading token will be taken as a literal SQL statement that will be used to test a connection.
Init SQL	The SQL code used to initialize a connection. If you specify a value for Init SQL, WebLogic Server will run the query when it creates a database connection. If no value is set for Init SQL, WebLogic Server does not run any SQL code to initialize the connection.Start the code with SQL followed by a space.
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.	Default: 10Dynamic: yes