[infinispan-issues] [JBoss JIRA] (ISPN-3287) Possible inconsistency with concurrent transactions during state transfer

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Tue Nov 19 08:41:06 EST 2013


    [ https://issues.jboss.org/browse/ISPN-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924873#comment-12924873 ] 

RH Bugzilla Integration commented on ISPN-3287:
-----------------------------------------------

Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 1024918|https://bugzilla.redhat.com/show_bug.cgi?id=1024918] from NEW to ON_QA
                
> Possible inconsistency with concurrent transactions during state transfer
> -------------------------------------------------------------------------
>
>                 Key: ISPN-3287
>                 URL: https://issues.jboss.org/browse/ISPN-3287
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Locking and Concurrency, State transfer
>    Affects Versions: 5.3.0.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Critical
>              Labels: 620
>             Fix For: 6.0.0.CR1, 6.0.0.Final
>
>
> It looks like there is a data race between the state transfer thread and a concurrent transaction in EntryWrappingInterceptor.commitEntryIfNeeded:
> tx: commitContextEntry()
> ST: stateConsumer.isKeyUpdated(k)? false
> tx: stateConsumer.addUpdatedKey(k)
> ST: commitContextEntry()
> We probably need some synchronization here, maybe using EquivalentConcurrentHashMapV8.computeIfAbsent().

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