[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-70) Transparent eager locking for transactions

Tue May 26 08:29:56 EDT 2009

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

Vladimir Blagojevic resolved ISPN-70.
-------------------------------------

    Resolution: Done

We agreed that the optimal solution, taking all trade offs into account, is to create a new interceptor. It just gets too messy if we subclass TxInterceptor since we have to then handle DistTxInterceptor and adding this functionality to LockingInterceptor blows it up quite a bit. 

Existing LockIterceptor#visitLockControlCommand (implemented for ISPN-48) has been augmented slightly to handle specific cases of implicit locking. 

A new interceptor was created - ImplicitEagerLockingInterceptor

> Transparent eager locking for transactions
> ------------------------------------------
>
>                 Key: ISPN-70
>                 URL: https://jira.jboss.org/jira/browse/ISPN-70
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Locking and Concurrency, Transactions
>            Reporter: Manik Surtani
>            Assignee: Vladimir Blagojevic
>             Fix For: 4.0.0.BETA1, 4.0.0.GA
>
>
> Allow a configuration attribute on <transaction /> to be able to specify whether cluster-wide locks are acquired eagerly or lazily.  The current scheme (lazy) should be the default.
> This could be implemented by broadcasting LockControlCommands alongside acquiring local locks for necessary keys.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira