JDBC Type 4 Driver 2.0 Programmer's Reference (SQL/MX 2.x)
Performance tip: HP recommends that you enable statement pooling for your JDBC applications
because this pooling can dramatically help the performance of many applications.
For example, to specify statement pooling, type: maxStatements=10
The Prepared Statement Caching algorithm is updatedfor each SQL prepared statement, a number is
assigned starting with one. The assigned number increments by one whenever the statement is prepared
again. This technique helps in selecting the prepared statements to be removed from the T4 driver cache.
The prepared statements, which are not in use but are in cache, are selected and sorted based on the
number assigned previously. The prepared statement, whose number is the least, is removed from the
cache.
minPoolSize Property
The minPoolSize property limits the number of physical connections that can be in the free
connection pool.
Set this property on a DataSource object, ConnectionPoolDataSource object, or
DriverManager object. For information about how to set properties, see How to Specify JDBC Type
4 Properties.
Data type: int
Default: -1 (The minPoolSize value is ignored.)
Range: -1, 0 through n, but less than maxPoolSize
Any negative value is treated like -1. Any value greater than maxPoolSize is changed to the
maxPoolSize value. The value of minPoolSize is set to -1 when maxPoolSize is -1. The value
determines connection pool use as follows:
When the number of physical connections in the free pool reaches the minPoolSize value, the
Type 4 driver closes subsequent connections by physically closing them—and not adding them to
the free pool.
●
0 (zero) means that the connections are not physically closed; the connections are always added to
the free pool when the connection is closed.
●
For example, use the following specification to set the minPoolSize value to 1, which ensures that
one connection is always retained:
minPoolSize=1
networkTimeout Property
The networkTimeout property sets a time limit that the driver waits for a reply from the database
server. When an operation is attempted for a period longer than the set value, in seconds, the driver stops
waiting for a reply and returns an SQLException to the user application.