db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronald Tschalaer (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4124) Broken double-checked-locking in EmbeddedDataSource.findDriver
Date Fri, 27 Mar 2009 07:38:50 GMT
Broken double-checked-locking in EmbeddedDataSource.findDriver
--------------------------------------------------------------

                 Key: DERBY-4124
                 URL: https://issues.apache.org/jira/browse/DERBY-4124
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.4.2.0
         Environment: all
            Reporter: Ronald Tschalaer


org.apache.derby.jdbc.EmbeddedDataSource.findDriver() uses the
double-checked-locking idiom for setting the 'driver' variable. This
idiom is, however, not correct and hence the code is broken. The fix
is to remove the outer if, i.e. to always enter the synchronized block.

See also
http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html

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