Connection Pooling with Apache DBCP

Question

I want to use Apache Commons DBCP to enable connection pooling in a Java Application (no container-provided DataSource in this). In many sites of the web -including Apache site- the usage of the library is based in this snippet:

BasicDataSource ds = new BasicDataSource();
ds.setDriverClassName("oracle.jdbc.driver.OracleDriver");
ds.setUsername("scott");
ds.setPassword("tiger");
ds.setUrl(connectURI);

Then you get your DB connections through the getConnection() method. But on other sites -and Apache Site also- the Datasource instance is made through this:

ConnectionFactory connectionFactory = new DriverManagerConnectionFactory(connectURI,null);
PoolableConnectionFactory poolableConnectionFactory = new PoolableConnectionFactory(connectionFactory);
ObjectPool objectPool = new GenericObjectPool(poolableConnectionFactory);
PoolingDataSource dataSource = new PoolingDataSource(objectPool);

What's the difference between them? I'm using connection pooling with BasicDataSource, or I need an instance of PoolingDataSource to work with connection pooling? Is BasicDataSource thread-safe (can I use it as a Class attribute) or I need to synchronize its access?

score 25 · Accepted Answer · edited Jul 17 '14 at 17:06

25

BasicDataSource is everything for basic needs. It creates internally a PoolableDataSource and an ObjectPool.

PoolableDataSource implements the DataSource interface using a provided ObjectPool. PoolingDataSource take cares of connections and ObjectPool take cares of holding and counting this object.

I would recommend using BasicDataSource. Only, If you really need something special maybe then you can use PoolingDatasource with another implementation of ObjectPool, but it will be very rare and specific.

BasicDataSource is thread-safe, but you should take care to use appropriate accessors rather than accessing protected fields directly to ensure thread-safety.

edited Jul 17 '14 at 17:06

Community

1
1

answered Jan 22 '13 at 21:19

ivi

316
4
6

What do you mean with "appropriate accessors"? Synchronized blocks? – Carlos Gavidia-Calderon Jan 22 '13 at 21:53
BasicDataSource is thread-safe, because all variables are read/written via synchronised. So, I don't think you need to use synchronize block. If you are extending this class you should just take care to use appropriate accessors,rather than accessing protected fields directly to ensure thread-safety, but you don't need to use synchronize blocks. – ivi Jan 22 '13 at 23:43

score 24 · Answer 2 · answered Sep 02 '13 at 12:45

This is more of a (big) supporting comment to ivi's answer above, but am posting it as an answer due to the need for adding snapshots.

BasicDataSource is everything for basic needs. It creates internally a PoolableDataSource and an ObjectPool.

I wanted to look at the code in BasicDataSource to substantiate that statement (which turns out to be true). I hope the following snapshots help future readers.

The following happens when the first time one does a basicDatasource.getConnection(). The first time around the DataSource is created as follows :

enter image description here

This is the raw connectionFactory.
This is the Generic Object Pool ('connectionPool') that is used in the remaining steps.
This combines the above two (connectionFactory + an Object Pool) to create a PoolableConnectionFactory.

Significantly, during the creation of the PoolableConnectionFactory, the connectionPool is linked with the connectionFactory like so:
Finally, a PoolingDataSource is created from the connectionPool

Connection Pooling with Apache DBCP

2 Answers2

Linked