[ 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. -- 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

[ https://issues.jboss.org/browse/ISPN-2384?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2384: -------------------------------- Fix Version/s: 5.2.0.CR1 5.2.0.Final -- 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

[ 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. -- 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

[ https://issues.jboss.org/browse/ISPN-2384?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2384: ----------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta3) -- 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

[ https://issues.jboss.org/browse/ISPN-2384?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2384: ----------------------------------- Forum Reference: http://lists.jboss.org/pipermail/infinispan-dev/2012-October/011614.html -- 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

[ https://issues.jboss.org/browse/ISPN-2384?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2384: ---------------------------------------- @Rado, I'm pretty sure it is. I think I have a fix for it, but needs some further work... -- 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

[ https://issues.jboss.org/browse/ISPN-2384?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2384: -------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta4) -- 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