What is Connection pool?
Connection pool is good for performance, as it prevents Java application create a connection each time when interact with database and minimizes the cost of opening and closing connections. The purpose is to reuse the connections and manage the process of opening, closing efficiently.
The shortcomings/disadvantages of Commons DBCP are very clearly documented over Tomcat 7.0 JDBC connection pool documentation.
See my other post (Tomcat 7: C3P0 Datasource Pool) summarizing how to Configure C3P0 in Tomcat 7.
Connection pool is good for performance, as it prevents Java application create a connection each time when interact with database and minimizes the cost of opening and closing connections. The purpose is to reuse the connections and manage the process of opening, closing efficiently.
The shortcomings/disadvantages of Commons DBCP are very clearly documented over Tomcat 7.0 JDBC connection pool documentation.
- commons-dbcp is single threaded, in order to be thread safe commons-dbcp locks the entire pool, even during query validation.
- commons-dbcp is slow - as the number of logical CPUs grow, the
performance suffers, the above point shows that there is not support
for high concurrency
Even with the enormous optimizations of the
synchronizedstatement in Java 6, commons-dbcp still suffers in speed and concurrency. - commons-dbcp is complex, over 60 classes. tomcat-jdbc-pool, core is 8 classes, hence modifications for future requirement will require much less changes. This is all you need to run the connection pool itself, the rest is gravy.
- commons-dbcp uses static interfaces. This means you can't compile it with JDK 1.6, or if you run on JDK 1.6/1.7 you will get NoSuchMethodException for all the methods not implemented, even if the driver supports it.
- The commons-dbcp has become fairly stagnant. Sparse updates, releases, and new feature support.
- It's not worth rewriting over 60 classes, when something as a connection pool can be accomplished with as a much simpler implementation.
- Tomcat jdbc pool implements a fairness option not available in commons-dbcp and still performs faster than commons-dbcp
- Tomcat jdbc pool implements the ability retrieve a connection asynchronously, without adding additional threads to the library itself
- Tomcat jdbc pool is a Tomcat module, it depends on Tomcat JULI, a simplified logging framework used in Tomcat.
- Retrieve the underlying connection using the javax.sql.PooledConnection interface.
- Starvation proof. If a pool is empty, and threads are waiting for a connection, when a connection is returned, the pool will awake the correct thread waiting. Most pools will simply starve.
See my other post (Tomcat 7: C3P0 Datasource Pool) summarizing how to Configure C3P0 in Tomcat 7.
