Table 23-1 JDBCMultiPool attributes
|
Attribute
|
Description
|
Range of Values and Default
|
|
ACLName
|
Deprecated. The access control list (ACL) used to control access to this MultiPool.
|
Required: no
|
|
AlgorithmType
|
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".
|
Admin Console field label: Algorithm Type
Required: no
Default: High-Availability
|
|
ConnectionPoolFailoverCallbackHandler
|
The absolute name of the application class that implements the interface weblogic.jdbc.extensions.ConnectionPoolFailoverCallback.
If set, before a MultiPool fails over to the next connection pool in the list, WebLogic Server calls the callback application indicated and waits for a return. Depending on the value returned from the callback application, the MultiPool will either try the same connection pool, failover to the next connection pool, or fail and throw an exception.
The MultiPool also calls the callback application when the original connection pool becomes available for failback.
|
Required: no
|
|
DeploymentOrder
|
A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.
Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.
|
Default: 1000
Minimum: 0
Maximum: 231-1
|
|
FailoverRequestIfBusy
|
Enables the MultiPool to failover to the next connection pool when all connections in the current connection pool are in use.
If set to true, when all connections in the current connection pool are in use, application requests for connections will be routed to alternate connection pools within the MultiPool.
If set to false, connection requests do not failover.
This is only relevant when running with the High Availability algorithm.
|
Default: false
|
|
HealthCheckFrequencySeconds
|
The frequency at which the MultiPool checks the health of connection pools that were previously found to be dead and were consequently disabled.
|
Default: 300
Maximum : MAXINT
Minimum: 0
Note: Setting the value to zero disables the attribute.
|
|
Name
|
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.
|
Admin Console field label: Name
Required: no
|
|
Notes
|
Optional information that you can include to describe this configuration.
|
Admin Console field label: Notes
Required: no
|
|
PoolList
|
The list of connection pools in the MultiPool.
|
Admin Console field label: Pool List
|
|
Targets
|
The targets in the current domain on which this item can be deployed.
|
Admin Console field label: Targets
Required: no
|
