JDBC MultiPool --> Configuration --> General
Tasks Related Topics Attributes
Overview
On the JDBC MultiPool
Note: MultiPools are not supported for use in distributed transactions. You cannot use connections from a connection pool within a MultiPool if the connection pool uses an XA driver to create database connections.
Tasks
Creating and Configuring a JDBC MultiPool
Deploying a JDBC MultiPool on One or More Servers and Clusters
Creating and Configuring a JDBC Connection Pool
Related Topics
Creating and Deploying JDBC Components - Connection Pools, MultiPools, and Data Sources
Attributes
|
Attribute Label |
Description |
Value Constraints |
|---|---|---|
| Name |
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management.
configuration. JDBCMultiPoolMBeanAttribute: Name |
|
| Algorithm Type |
The algorithm type for this Multipool. If set to "High availability", the connection pools are set up as an ordered list. That is, every time an application asks the Multipool for a connection, it tries to get a connection from the first pool in its list. If unable to get a valid connection, it tries the next pool in its list. The process is repeated until a valid connection is obtained, or until the end of the list is reached, in which case an exception will be thrown. Note that the Multipool will only move to the next pool in the list when there is a real problem with the pool, for example the database is down or the pool disabled. For the cases where all connections are busy, the Multipool behaves as a single pool and an exception is thrown. If the algorithm is set to "Load balancing," the Multipool will distribute the connection requests evenly to its member pools. This algorithm also performs the same failover behavior as the high availability algorithm. Default value for this attribute is "High availability".MBean: weblogic.management.
configuration. JDBCMultiPoolMBeanAttribute: AlgorithmType |
Default: High-AvailabilityValid values:
|
|
|
|