[infinispan-issues] [JBoss JIRA] (ISPN-2384) Entry lost after Eviction/Passivation
[
https://issues.jboss.org/browse/ISPN-2384?page=com.atlassian.jira.plugin....
]
Thomas Fromm updated ISPN-2384:
-------------------------------
Description:
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 :-/
was:
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.
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: Mircea Markus
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