[infinispan-issues] [JBoss JIRA] Updated: (ISPN-1340) ReadCommittedLock - commited Cache.remove is not visible to other transactions
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Fri Aug 19 07:14:17 EDT 2011
[ https://issues.jboss.org/browse/ISPN-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani updated ISPN-1340:
--------------------------------
Fix Version/s: 5.1.0.ALPHA1
5.1.0.FINAL
Priority: Critical (was: Major)
> ReadCommittedLock - commited Cache.remove is not visible to other transactions
> ------------------------------------------------------------------------------
>
> Key: ISPN-1340
> URL: https://issues.jboss.org/browse/ISPN-1340
> Project: Infinispan
> Issue Type: Bug
> Components: Locking and Concurrency
> Affects Versions: 5.0.0.FINAL
> Environment: jboss-6.0.0.Final, isolationlevel=READ_COMMITED
> Reporter: Marcel König
> Assignee: Manik Surtani
> Priority: Critical
> Fix For: 5.1.0.ALPHA1, 5.1.0.FINAL
>
> Attachments: ReadCommittedLockTest.java
>
>
> See the attached unit test: i added the testVisibilityOfCommittedDataRemove method to your org.infinispan.api.mvcc.read_committed.ReadCommittedLockTest unit test class.
> This test is successful in infinispan-4.2.1 but not in infinispan-5.0.0.
> What happens:
> 1. transaction1(tx1): cache.put("k", "v")
> 2. tx2: cache.remove("k")
> 3. tx2: commit
> 4. tx1: "v".equals(cache.get("k"))
> What should happen:
> ...
> 4. tx1: cache.get("k") == null
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list