[infinispan-issues] [JBoss JIRA] (ISPN-1555) Locks not released when using the lock API in a read-only transaction

[Manik Surtani (Updated) (JIRA)]

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

Manik Surtani updated ISPN-1555:
--------------------------------

              Summary: Locks not released when using the lock API in a read-only transaction  (was: locks not being released when transaction doesn't write)
        Fix Version/s: 5.1.0.CR1
     Git Pull Request: https://github.com/infinispan/infinispan/pull/677  (was: https://github.com/infinispan/infinispan/pull/677)
    Affects Version/s:     (was: 5.1.0.CR1)
          Description: 
{code}
tm.begin();
cache.getAdvancedCache().lock("k");
tm.commit(); 

assertNotLocked("k"); //this fails!!!
{code}
this transaction doesn't do any write, and we have an optimization in place to skip remote calls if we don't do any write. 


  was:
tm.begin();
cache.getAdvancedCache().lock("k");
tm.commit(); 

assertNotLocked("k"); //this fails!!!

this transaction doesn't do any write, and we have an optimization in place to skip remote calls if we don't do any write. 



    
> Locks not released when using the lock API in a read-only transaction
> ---------------------------------------------------------------------
>
>                 Key: ISPN-1555
>                 URL: https://issues.jboss.org/browse/ISPN-1555
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 5.1.0.BETA5
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>            Priority: Critical
>             Fix For: 5.1.0.CR1
>
>
> {code}
> tm.begin();
> cache.getAdvancedCache().lock("k");
> tm.commit(); 
> assertNotLocked("k"); //this fails!!!
> {code}
> this transaction doesn't do any write, and we have an optimization in place to skip remote calls if we don't do any write. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira