4 Replies Latest reply on Dec 9, 2004 5:21 AM by Sven Baumgarten

    optimistic locking conflicting update

    Sven Baumgarten Newbie

      I use optimistic locking on JBoss 4. If there are optimistic locking conflicting because data has already changed by another task I get an "org.jboss.tm.JBossRollbackException: Unable to commit" Exception.

      Is there any way to exactly determine wether a JBossRollbackException is caused by a optimistic locking conflict and not by any other?

      Why is there no OptimisticLockException like DeadlockException?