1. Home
  2. »
  3. Exception types
  4. »
  5. org
  6. »
  7. org.camunda
  8. »
  9. org.camunda.bpm
  10. »
  11. org.camunda.bpm.engine
  12. »
  13. OptimisticLockingException

OptimisticLockingException crashes

Collection of 10 web pages containing stack traces of org.camunda.bpm.engine.OptimisticLockingException

Find a solution to your bug here

This list contains all the bugs that lead to this exception. Click through to see the discussions about them.

  1. Cancelling asynchronous tasks

    via Google Groups by Harald Wellmann1 year ago
    MessageEntity[ccd99670-1b8c-11e3-adb9-c86000a34574] was updated by another transaction concurrently
  2. Receiving messages using Camel Integration and threading behavior

    via Google Groups by Unknown author1 year ago
    ExecutionEntity[8301] was updated by another transaction concurrently
  3. failedJobRetryTimeCycle and OptimisticLockingException

    via Google Groups by Unknown author1 year ago
    ExecutionEntity[a779ab6f-0bf1-11e4-9ac4-bc305bacc5da] was updated by another transaction concurrently
  4. Datasource configuration JBoss and Oracle

    via Google Groups by Unknown author1 year ago
    MessageEntity[a360ee54-1f79-11e4-aebf-b8ba20524153] was updated by another transaction concurrently
  5. please help org.camunda.bpm.engine.OptimisticLockingException: By Calling "identityService.saveUser(camundaUserEntity)"

    via Google Groups by Unknown author1 year ago
    UserEntity[kjkjlkjl] was updated by another transaction concurrently
  6. How to prevent OptimisticLockingException when executing service tasks concurrently?

    via Google Groups by Unknown author1 year ago
    ExecutionEntity[d1332687-d4e0-11e3-a07b-58946bf7bb18] was updated by another transaction concurrently
  7. Parallel Java Delegates causing deadlock when transitioning to end activity

    via Google Groups by Gareth1 year ago
    Could not execute UPDATE MessageEntity[804cb219-7317-11e5-8060-3e7a6115a7d6]. Entity was updated by another transaction concurrently
  8. Could not execute DELETE TimerEntity. Entity was updated by another transaction concurrently.

    via Google Groups by Emerald Hieu1 year ago
    Could not execute DELETE TimerEntity[6f3a43c6-7416-11e5-bbe6-000c2953c1d7]. Entity was updated by another transaction concurrently
  9. GitHub iconGitHub comment 1#292531292

    via GitHub by hawky-4s-1 year ago
    ENGINE-03005 Execution of 'DELETE MessageEntity[502]' failed. Entity was updated by another transaction concurrently.
  10. Duplicate variables allowed in ACT_RU_VARIABLE and FK constraint error

    via Google Groups by Galen Hollins3 years ago
    HistoricVariableInstanceEntity[8] was updated by another transaction concurrently

or use our map

We've collected millions of stack traces from the web.

We visualize these cases as a tree for easy understanding. We place your stack trace on this tree so you can find similar ones. The top nodes are generic cases, the leafs are the specific stack traces.

Paste your stack trace to find solutions with our map.