[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1364) data consistency issue with ReadUncommited

[Mircea Markus (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-1364?page=all ]

Mircea Markus updated JBCACHE-1364:
-----------------------------------

        Fix Version/s: 1.4.X
    Affects Version/s: 1.4.1.SP9
                       1.4.1.SP8
                           (was: 1.4.X)

> data consistency issue with ReadUncommited
> ------------------------------------------
>
>                 Key: JBCACHE-1364
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1364
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP8, 1.4.1.SP9
>            Reporter: Mircea Markus
>         Assigned To: Manik Surtani
>             Fix For: 1.4.X
>
>
> Scenario
>     * tx1 starts and create /a/b/c (results in following locks being acquired: rl for a and b and wl for c)
>     * tx2 starts and adds a key value under /a/b (acquires a WL on b, as for ReadUncommited WL does not wait for RL to be released)
>     * tx2 commits (so the key-value tx2 added under /a/b is there, correctly)
>     * tx1 rollabcks  FAILURE! - this will also delete the /a/b committed at the previous step
> the problem is that when creating a structural node (e.g. a and a/b) a RL is acquired. This is not correct, a WL should be acquired instead. (on 2.x series that's how it goes).
>  
> test added to reproduce the issue: IsolationLevelReadUncommitedTest (on 1.4.X branch)

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