What else is done in BES Jdbc connection pool (in addition to connection caching) ?
BES Jdbc pool provides seemless transaction integration between application server, and the underlying database. Basically, it is the responsibility of BES Jdbc pool to make sure that database transactions are driven (demarcated) by the transaction manager that is part of the AppServer. This means, BES connection pool, under the covers makes the Jdbc connection that is being dispensed from the connection pool, a transaction resource, and makes the connection available for re-use when the transaction ends.
