[infinispan-issues] [JBoss JIRA] (ISPN-4131) Lock acquired forever with delayed PrepareCommand

RH Bugzilla Integration (JIRA) issues at jboss.org
Mon May 12 10:31:59 EDT 2014


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

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

Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 1080314|https://bugzilla.redhat.com/show_bug.cgi?id=1080314] from ASSIGNED to MODIFIED

> Lock acquired forever with delayed PrepareCommand
> -------------------------------------------------
>
>                 Key: ISPN-4131
>                 URL: https://issues.jboss.org/browse/ISPN-4131
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 6.0.2.Final, 7.0.0.Alpha1
>            Reporter: Radim Vansa
>            Assignee: Dan Berindei
>            Priority: Critical
>              Labels: 630betablocker
>
> Distributed transactional cache:
> 1. A sends Prepare to B
> 2. B receives Prepare, but due to ongoing ST it is blocked
> 3. B replication timeout elapses
> 4. B sends Rollback, this does not find the TX as Prepare was not executed yet. The transaction is put into completedTransactions.
> 5. Completed transactions timeout elapses. This is by default 15 seconds, way shorter than ST timeout (due to which the Prepare was blocked)
> 6. Prepare is executed on B, acquiring lock on K
> Nobody will rollback the TX as originator thinks it was already rolled back.
> Result: key K will be locked forever, all attempts to update/remove it will fail.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


More information about the infinispan-issues mailing list