Hello everybody!
Cameron write please. How did you recreated mistake that the wrong
regions/caches were being updated?
I tried to do it in HibernateL2CacheConfigurationSelfTest.java -
testEntityCacheNonStrictFails.
After:
e2forUpdate.setName("XXX");
session.update(e2forUpdate);
Both
Hi,
Thank you for reporting this bug, but it seems fix you suggested will not
work for HibernateReadWriteAccessStrategy since single thread local is
needed to use single cross-cache transaction.
I created JIRA issue: https://issues.apache.org/jira/browse/IGNITE-4760.
Thanks!
On Sun, Feb 26,
I have just discovered that the ignite hibernate layer 2 cache region
factory does something weird with tracking changes - the wrong
regions/caches were being updated - I would end up with cache entries for
other regions in one region.
for example if I say loaded updated a product entity then
