[jboss-jira] [JBoss JIRA] (HIBERNATE-146) Remove after get with optimistic lock fails

Arcadiy Ivanov (JIRA) issues at jboss.org
Thu Sep 25 18:27:03 EDT 2014


Arcadiy Ivanov created HIBERNATE-146:
----------------------------------------

             Summary: Remove after get with optimistic lock fails
                 Key: HIBERNATE-146
                 URL: https://issues.jboss.org/browse/HIBERNATE-146
             Project: Hibernate Integration
          Issue Type: Bug
            Reporter: Arcadiy Ivanov
            Assignee: Steve Ebersole


Whenever an entity is retrieved with an optimistic lock and then later is removed within the same transaction, an OptimisticLockException is thrown incorrectly.

2014-09-25 13:59:00,674 WARN  [com.arjuna.ats.arjuna] (default task-64) ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< 0:ffffac11320f:1bba2f97:5422ecc6:1cd4, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization at 47f9da00 >: org.hibernate.OptimisticLockException: Newer version [null] of entity [[<Entity Class Name Here>#511]] found in database
  at org.hibernate.action.internal.EntityVerifyVersionProcess.doBeforeTransactionCompletion(EntityVerifyVersionProcess.java:60) [hibernate-core-4.3.5.Final.jar:4.3.5.Final]

This is caused by the lock being incorrectly tracked altogether.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)



More information about the jboss-jira mailing list