Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-12787

Non-transactional cache needs to be invalidated after commit on JPQL update/delete operation

XMLWordPrintable

      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.

              wburns@redhat.com Will Burns
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: