[
https://issues.apache.org/jira/browse/DBCP-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DBCP-300.
------------------------------
Resolution: Fixed
This has been fixed for DBCP 2.x onwards.
Earlier versions can't be fixed since double-checked locking requires Java 1.5+
to work correctly.
> remove synchronize access of createDataSource
> ---------------------------------------------
>
> Key: DBCP-300
> URL: https://issues.apache.org/jira/browse/DBCP-300
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.2.2, 1.3, 1.4
> Environment: RHEL, jdk1.5.0_12, commons-dbcp 1.2.2
> Reporter: Nikhil Singh
> Fix For: 2.0
>
>
> For JDK1.5 onwards we can make the DataSource volatile and start using
> "double checked locking" idiom. In my performance testing I have already
> started seeing wait time on this lock.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
