JDBC Driver for SQL/MP 3.0
Limits the number of physical connections that can be in the free connection pool. Specify the minPoolSize property
as:
int
The integer can be 0 through n, where n is the maximum integer value and less than maxPoolSize. The default is 0.
The value determines connection-pool use:
When the number of physical connections in the free pool reaches the minPoolSize value, the JDBC/MP driver
closes subsequent connections by physically closing the connections—not by adding them to the free pool.
Zero (0) means that minPoolSize is equal to maxPoolSize.
If MaxPoolsize is -1, the value of minPoolSize is ignored.
maxPoolSize Property
Sets the maximum number of physical connections that the pool can contain. These connections include those in both
the free pool and those in the use pool. When the maximum number of physical connections is reached, the JDBC/MP
driver throws an SQLException and reports the message, "Maximum pool size is reached." Specify the maxPoolSize
property as:
int
The integer can be -1, 0 through n, where n is the maximum integer value and greater than minPoolSize. The default
is 0. The value determines connection-pool use:
0 means no maximum pool size.
-1 indicates that connection pooling is disabled.
poolLogging Property
Indicates whether logging information about the state of the connection or statement pool should be written to the
logWriter. Specify the poolLogging property as:
boolean
The value can be true or false. True indicates that the information should be written; false indicates that no
information should be written.
This property is effective only if calling the DataSource.getLogWriter method does not return null.
TransactionMode Property
Sets the total transaction mode. Specify the TransactionMode property as:
string
The value can be either INTERNAL or EXTERNAL. The default is EXTERNAL. The value indicates transaction mode:
INTERNAL indicates that you want the JDBC/MP driver to manage transactions.
EXTERNAL indicates that you want the application to manage transactions by using JTA or the
com.tandem.tmf.Current class. For information on the com.tandem.tmf.Current class, see the
com.tandem.tmf package in the NonStop Server for Java API and Reference.