JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.1 (H06.23+, J06.12+)

when the connection is closed.
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 JDBC/MX driver throws an
SQLException with the message, "Maximum pool size is reached."
Specify the
maxPoolSize property as:
int
The integer can be -1, 0 through 2147483647, but greater than minPoolSize. The default is -1 (disables
connection pooling). The value determines connection pool use as follows:
Any negative value is considered as -1.
0 indicates no maximum pool size.
A value of -1 disables connection pooling.
transactionMode Property
The transactionMode property provides control over how and when transactions are performed. Specify the
transactionMode property as:
String
The default is mixed. The allowed values are:
internal
Specifies that transactions are always performed within a JDBC/MX driver-managed transaction. If an
external transaction exists when internal transaction mode is in effect, the external transaction is
suspended and the SQL statement is executed within a JDBC/MX driver-managed transaction. Upon
completion of the driver’s internally managed transaction, the existing external transaction is resumed.
The Connection autoCommit flag maintains a value of true when in internal transaction mode.
Note: Using
internal transactionMode for select statements performed in external transactions causes
JDBC/MX to throw an "invalid transaction state" exception. Therefore, do not specify
internal
transactionMode under these conditions.
mixed
Specifies that the driver inherits any active transaction in the current thread. The autocommit setting
of the transaction is ignored. The application must either commit or rollback the transaction in this
mode. If there is no active transaction, the driver creates one and begins the transaction, or aborts it
if there is an SQL error. In this mode, the driver supports both autocommit and non-autocommit. The
application ends the transaction in non-autocommit mode.
external
Specifies that if an external transaction exists, transactions are performed within the external
transaction. If an external transaction does not exist, the SQL statement is executed without a
transaction. This allows SQL statements that do not require an existing transaction to be performed
without one, providing an improvement in performance. If an SQL command requires a transaction
and no external transaction exists, an SQL exception is thrown.
Note: Using
external transactionMode for SQL statements that require execution within a transaction