OptimisticLockException when updating row with Oracle DATE mapped @Version property in Hibernate

Solution Verified - Updated -

Issue

  • An entity version property is defined as

        @Version
        private java.sql.Timestamp updatedAt;
    
  • The Oracle DATE type was chosen to map the version property when (manually) creating the underlying table in the database
  • Update fails (sometimes randomly) with a write failure

    javax.persistence.OptimisticLockException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1
    

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7
    • 6
  • Hibernate
    • 5
    • 4
  • Oracle

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