This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.

Configuring connection pooling for database connections

You can configure connection pooling for your data source by defining a connection manager for it.

Example

The following example code uses the connectionManager element in the server.xml file to define a connection pool for a data source:
<dataSource id="DefaultDataSource" jndiName="jdbc/example" jdbcDriverRef="DB2" >
  <connectionManager maxPoolSize="10" minPoolSize="2"/>
	<properties.db2.jcc databaseName="TESTDB"/>
</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 Tuning Liberty.

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

For more information about the connectionManager element, see **** MISSING FILE ****.


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: Tuesday, 12 December 2017
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=twlp_conn_pool
File name: twlp_conn_pool.html