JDBCMultiPool

JDBCMultiPool

Description

This MBean represents a JDBC Multipool, which is a pool of JDBC connection pools.

Syntax
<JDBCMultiPool


ACLName="String


AlgorithmType=( "High-Availability" | "Load-Balancing" )


DeploymentOrder="number


Name="String


Notes="String


PoolList="list of JDBCConnectionPool names


Targets="list of Target names


Type="String



/>
Parent Elements

Domain

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 TypeRequired: noDefault: High-Availability
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: 1000Minimum: 0Maximum: 2³¹-1
Name The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. Admin Console field label: NameRequired: no
Notes Optional information that you can include to describe this configuration. Admin Console field label: NotesRequired: 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: TargetsRequired: no
Type Returns the type of the MBean. Required: no

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 TypeRequired: noDefault: High-Availability
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: 1000Minimum: 0Maximum: 2³¹-1
Name	The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.	Admin Console field label: NameRequired: no
Notes	Optional information that you can include to describe this configuration.	Admin Console field label: NotesRequired: 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: TargetsRequired: no
Type	Returns the type of the MBean.	Required: no