You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/01 17:33:00 UTC
[jira] [Commented] (GEODE-6470) Double-checked locking is not
thread-safe [LGTM]
[ https://issues.apache.org/jira/browse/GEODE-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781900#comment-16781900 ]
ASF subversion and git services commented on GEODE-6470:
--------------------------------------------------------
Commit 97f5f9157843e2832ce52cae131d642c923c0e9a in geode's branch refs/heads/develop from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=97f5f91 ]
GEODE-6470: Making double-checked locking thread-safe (#3252)
* A repeated check on a non-volatile field is not thread-safe, and could result in unexpected behavior.
* Fixed using volatile and local variables
> Double-checked locking is not thread-safe [LGTM]
> ------------------------------------------------
>
> Key: GEODE-6470
> URL: https://issues.apache.org/jira/browse/GEODE-6470
> Project: Geode
> Issue Type: Bug
> Reporter: nabarun
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> A repeated check on a non-volatile field is not thread-safe, and could result in unexpected behavior
> References:
> [http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html]
> https://en.wikipedia.org/wiki/Double-checked_locking
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)