Configure connection pooling for database connections

We can configure connection pooling for the data source by defining a connection manager for it.

Subtopics

• How connection pooling configuration updates are applied
  If we change the attributes of the connectionManager element while a server is running, the updates to different attributes are applied at different times and in different ways.

Example

The following example code uses the connectionManager element in server.xml to define a connection pool for a data source:

<dataSource id="ds1" jndiName="jdbc/example" jdbcDriverRef="DB2" >
  <connectionManager maxPoolSize="10" minPoolSize="2" />
</dataSource>

The server uses default values for any connection management settings that are not defined on the connection manager element. If a connection manager is not defined at all for a data source, the server uses default values for all of the settings. Using thread local storage for connections can increase performance for applications on multi-threaded systems. See Tune the Liberty profile.

We can define multiple data sources and associate each with a different connection manager. However, we cannot associate multiple data sources with a single connection manager.

For more information about the connectionManager element, see Configuration elements in server.xml.

Parent topic: Configure database connectivity

Tasks:

Deploy an existing JDBC application to the Liberty profile