[infinispan-issues] [JBoss JIRA] Updated: (ISPN-20) check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE

Manik Surtani (JIRA) jira-events at lists.jboss.org
Mon Mar 15 13:16:38 EDT 2010


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

Manik Surtani updated ISPN-20:
------------------------------

    Fix Version/s: 5.1.0.BETA1
                   5.1.0.Final
                       (was: 5.0.0.BETA1)
                       (was: 5.0.0.Final)


> check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE
> ---------------------------------------------------------------------------------
>
>                 Key: ISPN-20
>                 URL: https://jira.jboss.org/jira/browse/ISPN-20
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Loaders and Stores, Locking and Concurrency
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>             Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores

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

        


More information about the infinispan-issues mailing list