Hibernate envers' RevisionNumber does not work under the clustering environment

Solution Verified - Updated -

Issue

There is a concern about Hivernate envers under clustering environment.(same application is used with multiple active runtimes)
Let's say
- runtime A does cache Revision Number 1～50
- runtime B does cache the Revision Number 51~100
- runtme B executes insert query // Revision number 51 is used
- runtime A executes update query // Revision number 1 is used
- This breaks the order of revision number.

How to avoid this situation?

Environment

  • Red Hat Fuse 7.8
    • Hibernate envers 5.3.17.Final-redhat-00001

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