[infinispan-issues] [JBoss JIRA] (ISPN-3956) L1WriteSynchronizer can cause locking with concurrent gets when value is not present
RH Bugzilla Integration (JIRA)
issues at jboss.org
Fri Mar 7 04:31:35 EST 2014
[ https://issues.jboss.org/browse/ISPN-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951013#comment-12951013 ]
RH Bugzilla Integration commented on ISPN-3956:
-----------------------------------------------
Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 1059814|https://bugzilla.redhat.com/show_bug.cgi?id=1059814] from MODIFIED to ON_QA
> 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
More information about the infinispan-issues
mailing list