-
Bug
-
Resolution: Done
-
Major
-
7.2.0.GA, 7.3.0.GA, 7.2.9.GA, 7.3.3.GA
-
None
-
False
-
False
-
-
-
-
-
-
+
-
Undefined
-
There was a change between EAP 7.1 and 7.2 in the handling of cache invalidation for JPAQL UPDATE or DELETE operations. In EAP 7.1 (using transactional caching), a post-commit invalidation of cached data occurred ensuring that subsequent data loads retrieved current state from the database. In EAP 7.2 and 7.3 (using non-transactional caching), invalidation occurs immediately and a load (from another thread) prior to database commit will leave stale data in the cache.
- clones
-
JBEAP-21276 [GSS](7.4.z) ISPN-12787 - Non Transactional Cache needs to be invalidated after commit on JPQL update/delete operation
- Closed
- is cloned by
-
ISPN-12787 Non-transactional cache needs to be invalidated after commit on JPQL update/delete operation
- Closed
- is incorporated by
-
JBEAP-21421 (7.3.z) Upgrade Infinispan from 9.4.22.Final-redhat-00001 to 9.4.23.Final-redhat-00001
- Closed
- blocks
-
HHH-14232 Loading...
- links to