Web container thread connection pool | Prepared statement cache
17.2 Database connection pool
Overview
Unlike the recommendation in the WAS InfoCenter, which states that the database connection pool should be smaller than the Web container thread pool, for WebSphere Commerce configurations, each WebSphere Web container thread needs at least one database connection to match.
In addition, when Commerce Scheduler is being used, an additional database connection needs to be reserved to ensure that the WebSphere Commerce scheduler threads function properly.
The database connection pool default is 5-6 connections. In general, you should have at least one database connection per Web container thread. If you are using the Commerce Scheduler, one additional connection is necessary.
Set the data source connections
JDBC providers | skyway - WebSphere Commerce JDBC Provider | Data sources | WebSphere Commerce DB2 DataSource skyway | Connection pools