a named group of JDBC connections to a database that are created when the WebLogic Server starts
an object designed to provide thread-safe access to a limited number of database connections in a multithreaded environment
a service that creates and maintains a shared collection (pool) of data source connections on behalf of one or more clients
a set of database connections managed by the application server for the various applications it manages
a set of database connections that are available for an application to use
A collection of communication links to back-end data sources, such as 3270 applications or databases. When an Integration Object is run on behalf of a client request, the Integration Object obtains an available connection from a pool, uses it for access to the data source, then returns the connection to the pool for reuse by another Integration Object. When connections are pooled, the overhead of establishing a connection is absorbed in its first use. Each Integration Object reusing this connection benefits from the prior establishment of the connection and can run faster. (See also connection pooling.)
The connection pool is the collection of open connections. This pool has a limit to how many connections are allowed to be open at the same time. If the limit is reached, the pool will make any connection requests wait until one of the connections in the pool is closed, and a spot becomes free.
A Connection Pool is a cache of database connections maintained in the database's memory so that the connections can be reused when the database receives future requests for data.