Neoview JDBC Type 4 Driver Programmer's Reference (R2.2, R2.3, R2.4, R2.5)

Connection Pooling
The Type 4 driver provides an implementation of connection pooling, where a cache of physical
database connections are assigned to a client session and reused for the database activity. If
connection pooling is active, connections are not physically closed. The connection is returned
to its connection pool when the Connection.close() method is called. The next time a
connection is requested by the client, the driver will return the pooled connection, and not a new
physical connection.
• The connection pooling feature is available when the JDBC application uses either the
DriverManager class or DataSource interface to obtain a JDBC connection. The connection
pool size is determined by the maxPoolSize property value and minPoolSize property
value.
• By default, connection pooling is disabled. To enable connection pooling, set the
maxPoolSize property to an integer value greater than 0 (zero).
• Manage connection pooling by using these Type 4 driver properties:
— maxPoolSize under “maxPoolSize Property” (page 44)
— minPoolSize under “minPoolSize Property” (page 45)
— initialPoolSizeunder “initialPoolSize Property” (page 41)
— maxStatements under “maxStatements Property” (page 44)
• When used with the DriverManager class, the Type 4 driver has a connection-pool manager
that determines which connections are pooled together by a unique value for these
combination of properties:
url
catalog
schema
username
password
serverDataSource
Therefore, connections that have the same values for the combination of a set of properties
are pooled together.
NOTE: The connection-pooling property values used at the first connection of a given
combination are effective throughout the life of the process. An application cannot change
any of these property values after the first connection for a given combination.
Connection Pooling 27