commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <>
Subject [jira] Commented: (DBCP-300) remove synchronize access of createDataSource
Date Fri, 11 Sep 2009 08:23:57 GMT


Mark Thomas commented on DBCP-300:

Which version of commons-pool?
Which lock do you see contention on?

Locking is mostly a POOL rather than DBCP issue. A move to jdk 1.5 would allow the use of
j.u.concurrent which will would be a significant change to the locking implementation.

> remove synchronize access of createDataSource
> ---------------------------------------------
>                 Key: DBCP-300
>                 URL:
>             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
> 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message