[
https://issues.jboss.org/browse/ISPN-1935?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1935:
-----------------------------------
Forum Reference:
https://community.jboss.org/thread/197126?tstart=0,
http://lists.jboss.org/pipermail/infinispan-dev/2012-March/010471.html (was:
https://community.jboss.org/thread/197126?tstart=0)
Adding a dev list discussion for this. It doesn't seem to have an easy fix.
The reason for getting 4 notifications is cos you get a notification for operations on the
internal structure, and internal data holder generation. So, for a a k,v put on /root,
you'd get:
- "/" structure modified
- "/root" structure modified
- data in "/" initialized with empty map
- data in "/root" initialized with empty map
Notification CacheEntryModified in combination with Tree API always
contains an empty AtomicHashMap
---------------------------------------------------------------------------------------------------
Key: ISPN-1935
URL:
https://issues.jboss.org/browse/ISPN-1935
Project: Infinispan
Issue Type: Bug
Components: Core API, Tree API
Affects Versions: 5.1.2.FINAL
Reporter: Michael Gronau
Assignee: Galder Zamarreño
Labels: API, CacheEntryModified, Notifications, TreeCache
Fix For: 5.1.3.FINAL
A put operation to the TreeCache API causes multiple CacheEntryModified events to be
fired. The data map (an AtomicHashMap) is always empty and does not contain the
modifications. The notifications are fired twice for isPre=false and isPre=true, which
means they are fired 4 times.
--
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