Ensuring High Level of Performance with WebLogic JDBC Connection Pools
Written by Purushotham In this post, you will find some common best practices aimed at ensuring high levels of performance with WebLogic JDBC. Use WebLogic DataSources for connection pooling of JDBC connections Making a real DBMS connection is expensive and slow, so you should use our data sources to retain and re-use connections. The ideal mode for using pooled connections is to use them as quickly and briefly as possible, getting them just when needed, and closing them (returning them to the pool) as soon as possible. This maximizes concurrency. (It is crucial that the connection is a method-level object, not shared between application threads, and that it *is* closed, no matter what exit path the application code takes, else the pool could be leaked dry, all connections taken out and abandoned. See a best-practices code example farther down in this article. The long-term hardening and integration of WebLogic Datasources with applications and other WebLogic AP