Transactional AtomicHashMap modifications are lost when persisting

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.