[infinispan-issues] [JBoss JIRA] (ISPN-1935) Notification CacheEntryModified in combination with Tree API always contains an empty AtomicHashMap
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Tue Mar 27 07:15:49 EDT 2012
[ https://issues.jboss.org/browse/ISPN-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679573#comment-12679573 ]
Galder Zamarreño edited comment on ISPN-1935 at 3/27/12 7:14 AM:
-----------------------------------------------------------------
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
was (Author: galder.zamarreno):
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
More information about the infinispan-issues
mailing list