You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2009/09/13 19:39:57 UTC

[jira] Updated: (DBCP-300) remove synchronize access of createDataSource

     [ https://issues.apache.org/jira/browse/DBCP-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Thomas updated DBCP-300:
-----------------------------

    Fix Version/s: 2.0

API change -> bump to 2.0

> 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
>         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.
-
You can reply to this email to add a comment to the issue online.