[infinispan-issues] [JBoss JIRA] Updated: (ISPN-419) Transactional AtomicHashMap modifications are lost when persisting

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno updated ISPN-419:
----------------------------------

        Summary: Transactional AtomicHashMap modifications are lost when persisting  (was: Transactional AtomicHashMap modifications are lost when replicating or persisting)
    Description: 
When an AtomicHashMap stored in a cache store using transactions, the actual modification is lost.

This is due to duplication of modifications being fired. After the 1st modification has been sent to another node or cache store, its delta is reset and when the 2nd modification comes, it finds delta as being null and hence that's what's replicated stored.

  was:
When an AtomicHashMap is either replicate or stored in a cache store using transactions, the actual modification is lost.

This is due to duplication of modifications being fired. After the 1st modification has been sent to another node or cache store, its delta is reset and when the 2nd modification comes, it finds delta as being null and hence that's what's replicated stored.



The issue only affects persistence via cache store.

> Transactional AtomicHashMap modifications are lost when persisting
> ------------------------------------------------------------------
>
>                 Key: ISPN-419
>                 URL: https://jira.jboss.org/jira/browse/ISPN-419
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.0.0.Final, 4.1.0.ALPHA3
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.1.0.BETA1
>
>
> When an AtomicHashMap stored in a cache store using transactions, the actual modification is lost.
> This is due to duplication of modifications being fired. After the 1st modification has been sent to another node or cache store, its delta is reset and when the 2nd modification comes, it finds delta as being null and hence that's what's replicated stored.

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