JDBC MultiPool --> Configuration --> General

Name

The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.

MBean: weblogic.management.
configuration.
JDBCMultiPoolMBean

Attribute: 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 by default, 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. (With WebLogic Server 8.1SP3 and later releases, you can enable failover when a connection pool is busy. See "MultiPool Failover Enhancements" in Programming WebLogic JDBC for more information.)

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.
JDBCMultiPoolMBean

Attribute: AlgorithmType

Default: High-Availability

Valid values:

• High-Availability

• Load-Balancing