The JDBC Pool Manager rule tunes a JDBC connection pool's values for Maximum Pool Size (max-pool-size) and for Initial and Minimum Pool Size (steady-pool-size). These recalculations happen only during runtime, and absolute recalculated values are not reflected anywhere. In production environments, recalculations are based only on the number of client requests for Initial and Minimum Pool Size, and only on server instance addition or deletion for Maximum Pool Size.
The JDBC Pool Manager rule includes the following rule-specific settings:
Default Max Connections — Specify the default maximum connection pool size setting for pools with no pool-specific setting. The default is 32.
Sampling Frequency — Specify the frequency in seconds at which JDBC connection pools are checked for the number of connections. The default is 60.
Number of Samples — Specify the number of samples used to determine a moving average value for the number of connections. The default is 5.
JDBC Pools Table — Either check the box next to * (applies to All Current and Future JDBC Connection Pools) or check boxes next to individual connection pools. For each selected pool, enter a Max Connections value or leave Max Connections blank to use the default.
Do not select both * (applies to All Current and Future JDBC Connection Pools) and individual connection pools. The Max Connections setting for * (applies to All Current and Future JDBC Connection Pools) overrides the Max Connections settings for individual connection pools.
All the Max Connections settings in this rule, including Default Max Connections and the Max Connections settings for individual pools, override the Maximum Pool Size settings for the JDBC connection pools.
For general steps on how to configure a rule, see Using the Management Rules.