-
Bug
-
Resolution: Done
-
Major
-
11.0.9.Final
-
None
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-20264 [GSS](7.3.z) ISPN-12787 - Non Transactional Cache needs to be invalidated after commit on JPQL update/delete operation
- Closed