For best stability and performance, configure the pool to create all the connections it will need during startup, and retain them indefinitely. Hence, set the initial capacity to equal the maximum capacity, which would be identical for each execute-thread. Connection pooling provided by WebLogic Server data sources improves performance, by making a pool of connections available for JDBC applications. Connections do not have to be opened and closed for each client.

Test Connections on Reserve tests the connections before making a connection available to a client and can reduce the performance. To prevent frequent connection testing, set the connection pool attribute, Seconds to Trust an Idle Pool Connection. This attribute specifies the number of seconds for which a connection that is known to have been successfully used, is not tested with a SQL query. When JDBC is done in external client JVMs, using RMI to do JDBC through WebLogic to the DBMS, data source performance...