commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dapper Dano (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DBCP-300) remove synchronize access of createDataSource
Date Wed, 21 Jul 2010 22:39:49 GMT

    [ https://issues.apache.org/jira/browse/DBCP-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890939#action_12890939
] 

Dapper Dano commented on DBCP-300:
----------------------------------

Is there going to be any focus on this issue soon?  This can cause quite a few blocked threads
if a datasource is timing out, as the first thread will block all others while attempting
to connect (21 seconds by default).  After the first times out, the next one attempts to connect
while the remaining wait and so on.  This can cause quite a back up.

In the mean time, has anyone found a workaround or alternative substitution for pools in the
tomcat application context?

> 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.


Mime
View raw message