[
https://jira.jboss.org/browse/ISPN-618?page=com.atlassian.jira.plugin.sys...
]
Sanne Grinovero commented on ISPN-618:
--------------------------------------
Still not good, we are not testing relations between transactional and non-transactional
Modifications, and the current one is actually reordering the two set of
"coalesced" Modification sets.
For example:
TX1 adds some things, then an out-of-transaction clear() is issued, we could ->
clear(), apply TX1
I think this strategy is getting too hard to get right, I'm going to try the other
approach.
AsyncStore fails to save all values when using transactions or batch
operations
-------------------------------------------------------------------------------
Key: ISPN-618
URL:
https://jira.jboss.org/browse/ISPN-618
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 4.1.0.CR3
Reporter: Sanne Grinovero
Assignee: Mircea Markus
Priority: Critical
Fix For: 4.1.0.Final, 5.0.0.BETA1
Attachments: AsyncStoreBatchingFailsUT.patch, AsyncStoreStopsBeforeSaveUT.patch,
suggested_fix_with_failing_tests.patch
It doesn't seem to be time-related, as the data is lost even when waiting a bit.
I'm attaching a unit test which applies to core and shows the problem using an async
FileCacheStore.
Attached testcase uses batching, but the same should apply when using transactions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira