Database Reference
In-Depth Information
Table 15-2. FCF API Parameters
Parameter
Description
MinLimit
The minimum number of connection (default value is 0) instances the cache
holds at all times. This value will not initialize the cache with the specified
number of connections. The InitialLimit is used for the initial number of
connection instances for the cache to hold.
MaxLimit
The maximum number (default 0) of connection instances the cache can hold.
MaxStatementsLimit
The maximum number of statements that a connection keeps open.
InactivityTimeout
The maximum time that a physical connection can be idle in connection cache.
Value specified is in seconds (default 0).
TimeToLiveTimeout
The maximum time in seconds that a logical connection can remain open.
When TimeToLiveTimeout expires, the logical connection is unconditionally
closed, the relevant statement handles are canceled, and the underlying physical
connection is returned to the cache for reuse.
AbandonedConnectionTimeout
The maximum time (default 0) that a connection can remain unused before the
connection is closed and returned to the cache.
PropertyCheckInterval
The time interval (default value of 900 seconds) at which the cache manager
inspects and enforces all specified cache properties.
ConnectionWaitTimeout
Specifies cache behavior when a connection is requested and there are already
MaxLimit connections active. If ConnectionWaitTimeout is greater than 0,
each connection request waits for the specified number of seconds, or until a
connection is returned to the cache. If no connection is returned to the cache
before the timeout elapses, the connection request returns null. This parameter
has a default value of 0 and basically no timeout occurs.
ValidateConnection
Setting this to true causes the connection cache to test every connection it
retrieves against the underlying database (default = false).
ClosestConnectionMatch
Setting this to true causes the connection cache to retrieve the connection with
the closest approximation to the specified connection attributes. This can be used
in combination with AttributeWeights to specify what is considered a “closest
match” (default = false).
AttributeWeights
Sets the weights for each connection attribute used when
ClosestConnectionMatch is set to true to determine which attributes are given
highest priority when searching for matches. An attribute with a high weight
is given more importance in determining a match than an attribute with a low
weight. AttributeWeights contains a set of key/value pairs that set the weights
for each connection attribute for which the user intends to request a connection.
The key is a connection attribute and the value is the weight; a weight must be an
integer value greater than 0. The default weight is 1.
Dynamic cleaning of the connections to the failed node eliminates the delay in realizing that the connections
are stale and to establish the connections to stable/backup node, thus improving the failover time dramatically.
Note
 
Search WWH ::




Custom Search