JDBC Type 4 Driver 1.1 Programmer's Reference

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.
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.
Note: Be careful when using this property. A network timeout causes the socket connection
between the Type 4 driver and the MXCS server to timeout. If the server is engaged
in a transaction or an SQL operation, then the server continues to perform that
transaction or operation until the transaction or operation fails, TMF times out, or the
server realizes that the Type 4 driver client has gone away. A network timeout can
result in an open transaction or operation that continues for a significant time before
failing or rolling back.
As a result of a network timeout, the connection becomes unavailable.
Data type: int
Units: seconds
Default: 0 (No network timeout is specified.)
0 through to 2147483647