JDBC object pooling

Object pooling is the most common topic to come up when discussing Java™ Database Connectivity (JDBC) and performance. Since many objects used in JDBC are expensive to create such as Connection, Statement, and ResultSet objects, significant performance benefits can be achieved by reusing these objects instead of creating every time you need them.

Many applications already handle object pooling on your behalf. For example, WebSphere^® has extensive support for pooling JDBC objects and allows you to control how the pool is managed. Because of this, you can get the functionality you want without being concerned about your own pooling mechanisms. However, when the support is not provided, you must find a solution for all but trivial applications.

• Use DataSource support for object pooling
  You can use DataSources to have multiple applications share a common configuration for accessing a database. This is accomplished by having each application reference the same DataSource name.
• ConnectionPoolDataSource properties
  You can configure the ConnectionPoolDataSource interface by using the set of properties that it provides.
• DataSource-based statement pooling
  The maxStatements property, available on the UDBConnectionPoolDataSource interface, allows for statement pooling within the connection pool. Statement pooling only has an effect on PreparedStatements and CallableStatements. Statement objects are not pooled.
• Build your own connection pooling
  You can develop your own connection and statement pooling without requiring support for DataSources or relying on another product.