Local Infinispan level 2 cache for Hibernate contains stale data following transaction rollback in JBoss EAP

Solution Verified - Updated -

Issue

  • Using Infinispan for level 2 cache for Hibernate.
  • When a transaction changes an entity and that transaction is, subsequently, rolled back, the changes are nonetheless put into the second level cache.
  • Subsequent cache reads will retrieve the stale/incorrect data.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.2
  • Infinispan 9.3
  • Hibernate 5.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content