JDBC Driver for SQL/MX Programmer's Reference

initialPoolSize int
The number of physical connections the pool
should contain when it is created.
minPoolSize int
The number of physical connections the pool
should keep available at all times. 0 (zero)
indicates no maximum size.
maxPoolSize int
The maximum number of physical connections
that the pool should contain. 0 (zero) indicates
no maximum size.
maxIdleTime int
The number of seconds that a physical
connection should remain unused in the pool
before the connection is closed. 0 (zero)
indicates no limit.
propertyCycle int
The interval, in seconds, that the pool should
wait before enforcing the current policy defined
by the values of the above connection pool
properties.
Connection Pooling Using the Basic DataSource
API
For your JDBC application to enable connection pooling, use the basic DataSource interface,
which includes the following properties that control connection pooling:
maxPoolSize❍
minPoolSize❍
maxStatements❍
Your application can enable connection pooling in the following two ways:
By setting the dataSourceName property in the basic DataSource object to the
previously registered ConnectionPoolDataSource object. When the connection
pooling is enabled, the JDBC/MX driver-specific properties in the
ConnectionPoolDataSource object are effective, and the JDBC/MX driver-specific
properties in the DataSource object are ignored. The connection is initialized with the
JDBC/MX driver-specific properties when the PooledConnection is obtained.
●
By using the properties in the DataSource object, when the dataSourceName property
is empty. Connection pooling is enabled by default. Note that the default value for the
maxPoolSize property is 0, which enables connection pooling. See the DataSource
interface for the details on using these properties.
●
For troubleshooting application connection pooling, note the following details on how the feature is
implemented. JDBC/MX looks for the first available PooledConnection object and assigns the