[infinispan-issues] [JBoss JIRA] (ISPN-3956) L1WriteSynchronizer can cause locking with concurrent gets when value is not present

[William Burns (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Burns updated ISPN-3956:
--------------------------------

              Status: Pull Request Sent  (was: Coding In Progress)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/2361

    
> L1WriteSynchronizer can cause locking with concurrent gets when value is not present
> ------------------------------------------------------------------------------------
>
>                 Key: ISPN-3956
>                 URL: https://issues.jboss.org/browse/ISPN-3956
>             Project: Infinispan
>          Issue Type: Bug
>          Components: L1
>    Affects Versions: 6.0.0.Final
>            Reporter: William Burns
>            Assignee: William Burns
>             Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
>
> This has been seen previously only on IBM JDK 6 ISPN-3889, however an end user also now can reproduce this issue https://community.jboss.org/thread/236590
> The issue is that we don't set the remote lookup value to be null when nothing is found and thus any threads that are waiting for the remote lookup were never notified of this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira