[infinispan-issues] [JBoss JIRA] (ISPN-1908) Invalid CacheStore content when using DIST_SYNC + shared CacheStore and Transactions
[
https://issues.jboss.org/browse/ISPN-1908?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1908:
----------------------------------------
@Thomas, this is indeed a bug. What seems to happen is when DIST_SYNC and transactions are
in use, if the originator should not store the data in the cache store, it skips it (which
is right), but the owner of the data, which receives the prepare, is not actually calling
into the cache store.
Basically, when the prepare() is called locally, CacheStoreInterceptor.skip() returns
false and so it's able to determine whether the put call should be stored or not.
However, when that's executed remotely, it returns true and so the
DistCacheStoreInterceptor is not able to check whether it's the owner of the key and
it should store it. I'm trying to figure out a fix for this (i.e. override
visitPrepareCommand in DistCacheStoreInterceptor...)
Invalid CacheStore content when using DIST_SYNC + shared CacheStore
and Transactions
-------------------------------------------------------------------------------------
Key: ISPN-1908
URL: https://issues.jboss.org/browse/ISPN-1908
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.1.2.FINAL
Reporter: Thomas Fromm
Assignee: Galder Zamarreño
Priority: Critical
Fix For: 5.1.3.CR1, 5.1.3.FINAL
Attachments: XXX.java
The attached file is an example to reproduce the situation:
CM1 is started and a cache is filled up with some values. 2nd CM is now started and the
same cache is filled there with values. As result I'd expect to have (in this case) 8
entries inside the cache store.
When using JDBC cache store and looking into the logs, for some of the key added in the
2nd node (even if they are unique) he executes UPDATE queries instead of inserts...
This only happens, when cache store is shared and transactions are enabled.
--
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