[
https://issues.jboss.org/browse/ISPN-2384?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-2384:
----------------------------------------
@Thomas, thanks for the report. I think I can see what's happening:
Once an entry is to be evicted, it's going to be passivated and stored in the cache
store before removing it from memory. In the logs, once the passivation kicks in, another
thread in arrives and retrieves the key from memory, triggering an activation, which
removes the entry from the store. In the cache store, the passivation store happens first,
then the activation logic to remove it, and the eviction of the beginning removes the
entry from memory. The result is that data is gone.
Activation logic looks a bit primitive removing entries indiscriminately, but I'm
looking at other possibilities to fix this.
Entry lost after Eviction/Passivation
-------------------------------------
Key: ISPN-2384
URL:
https://issues.jboss.org/browse/ISPN-2384
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 5.2.0.Beta1
Reporter: Thomas Fromm
Assignee: Galder Zamarreño
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: eviction.log
Cache is LOCAL, eviction + passivation enabled. After put the entry gets passivated,
shortly after an other thread tries to get() the entry, but get null.
Attached a log file. The key is "50b2c9e7-0a38-0043-01fc-76cdf49fa2ce". Tried
JDBC and File store with same results, also sync/async store tested. It happens under some
load.
I wasn't successful to create unit test for reproduction :-/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira