Administration Console Online Help
|
 |
 |
|
|
JDBC Connection Pool --> Control
Overview
On this tab, you can manually control each instance of the connection pool, including the following options:
Shrink—Shrinks the connection pool to the greater value of either the currently reserved connections or the initial size. Shrinking must be enabled on the Configuration
Reset—Resets the database connection pool by shutting down and re-establishing all available database connections. This also clears the statement cache for each connection in the connection pool. You can only reset a normally running connection pool.
Clear Statement Cache—Clears the cache of prepared and callable statements maintained for each connection in the pool.
Suspend—Disables the pool, suspending all operations on pool connections until the pool is re-enabled. All connections are preserved exactly as they were before the connection pool was suspended. If connections are in use, applications using a connection will get an exception.
Force Suspend—Forcibly disables the pool, suspending all operations on pool connections until the pool is re-enabled. All current users of the pool are forcibly disconnected and all connections that were in use when the connection pool was suspended are recreated (closed and reopened). Any transaction on the connections that are closed are rolled back. All other connections are preserved exactly as they were before the connection pool was suspended.
Destroy—Closes all database connections and deletes the configuration from the configuration file. If any connections from the pool are currently in use, the operation will fail.
Force Destroy—Forcibly destroys the pool. Forcibly disconnects all current users of the pool. Closes all database connections and deletes the configuration from the configuration file.
Resume—Restores all access to and operations on the pool. Only available after the connection pool is successfully suspended.
Note: You cannot restart a connection pool from this page that did not start correctly at server startup or when deploying the connection pool. Instead you must undeploy and redeploy the pool on the target servers and clusters on which the pool did not start correctly. See Restarting a JDBC Connection Pool.
Tasks
Shrinking a JDBC Connection Pool
Resetting All Connections in a JDBC Connection Pool
Suspending a JDBC Connection Pool
Resuming a JDBC Connection Pool
Shutting Down a JDBC Connection Pool
Restarting a JDBC Connection Pool
Destroying or Deleting a JDBC Connection Pool
Clearing the Statement Cache for a JDBC Connection Pool
Related Topics
Managing JDBC Connection Pools
