Why is DBCP still used instead of other Connection Pools?

Question

After reading this article - "Connection pooling options with JDBC: DBCP vs C3P0"; About how Apache DBCP is out of date, not production graded and not supported by hibernate, I'm confused why people are still using it instead other connection pools like C3P0?

For example: In this tutorial created May 2012 - Spring Hibernate Integration Tutorial

<bean id="myDataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close"> ... </bean>

Because not everything that people write in stack overflow is gold. — anttix, Jul 28 '12 at 02:18
I prefer rathen Tomcat JDBC Pool. It is superior to Commons DBCP. — Michael-O, Jul 28 '12 at 17:20

score 0 · Answer 1 · answered Jul 28 '12 at 06:59

0

The article you linked to says:

UPDATE: It turns out that after many years of sitting on a shelf, the Apache Commons folk have taken DBCP out of dormancy and it is now, once again, an actively developed project. Thus my original post may be out of date.

So, maybe the issues in the article have been met by others, or maybe they've been fixed now. Make up your own opinion.

answered Jul 28 '12 at 06:59

JB Nizet

678,734
91
1,224
1,255

Yes good pick up. Looking at http://commons.apache.org/dbcp/ the last updated date is 25 November 2010 on Version: 1.4.1-SNAPSHOT which is 1.5 years ago.. And in this article http://wiki.apache.org/commons/DBCP/Hibernate published on Jan 2011 it mentions limited support for DBCP on Hibernate 2. – JackDev Jul 28 '12 at 09:29

Why is DBCP still used instead of other Connection Pools?

1 Answers1