JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2 (H06.25+, J06.14+)

If set to 0 (zero), no login timeout is specified. If set to a value more than the specified range such
as 330000, the following error message is displayed:
Invalid connection property setting: Provided LoginTimeout property
value 33000 is invalid and should be less than Short.MAX_VALUE(32767.
maxIdleTime
NOTE: The maxIdleTime property is available in the V11^AAC and subsequent Software
Product Releases (SPRs).
The maxIdleTime property determines the number of seconds that a physical connection must
remain unused in the pool before the connection is closed. 0 (zero) indicates no limit.
Set this property on a DataSource object, ConnectionPoolDataSource object, or
DriverManager object.
Data type: int
Units: seconds
Default: 0 (No timeout)
Range: 0 through 2147483647
Any negative value is treated as 0, which indicates that no time limit applies.
For example, to set the maximum idle time to 5 minutes (300 seconds):
java –Dt4sqlmx.maxIdleTime=300
maxPoolSize
The maxPoolSize property sets the maximum number of physical connections that the pool can
contain. These connections include both free connections and connections in use. When the
maximum number of physical connections is reached, the Type 4 driver throws an SQLException
and sends the message, Maximum pool size is reached.
Set this property on a DataSource object, ConnectionPoolDataSource object, or
DriverManager object.
Data type: int
Units: number of physical connections
Default: -1 (Disables connection pooling.)
Range: -1, 0 through 2147483647, but greater than minPoolSize
The value determines connection-pool use as follows:
Any negative value is treated like -1.
0 means no maximum pool size.
A value of -1 disables connection pooling.
Any positive value less than minPoolSize is changed to the minPoolSize value.
maxStatements
The maxStatements property sets the total number of PreparedStatement objects that the
connection pool must cache. This total includes both free objects and objects in use. The JDBC T4
driver side cache uses the Most Frequently Used (MFU) or the Most Recently Used (MRU) algorithms.
MFU is the default setting. For more information on selecting the algorithm that you want, see
“mfuStatementCache” (page 45).
44 Type 4 Driver Properties