[infinispan-issues] [JBoss JIRA] (ISPN-2075) WriteSkewCheck failures when an AtomicMap is removed in the same transaction in which it was created
Sanne Grinovero (JIRA)
jira-events at lists.jboss.org
Tue May 29 10:07:19 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696821#comment-12696821 ]
Sanne Grinovero commented on ISPN-2075:
---------------------------------------
To point out:
there are no contending transactions, no transactions being suspended, in fact it all happens in the same thread in "plain" sequential order, still this fails with a
{quote}CacheException: Detected write skew - concurrent removal of entry!{quote}
> WriteSkewCheck failures when an AtomicMap is removed in the same transaction in which it was created
> ----------------------------------------------------------------------------------------------------
>
> Key: ISPN-2075
> URL: https://issues.jboss.org/browse/ISPN-2075
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 5.1.5.CR1
> Reporter: Sanne Grinovero
> Assignee: Manik Surtani
> Fix For: 5.1.5.FINAL, 5.2.0.ALPHA1
>
>
> I guess the use case might sound surprising, but after stewing long OGM logs, this seems to be a frequent use case.
> I'll attach a functional test.
--
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
More information about the infinispan-issues
mailing list