Uses of Class
org.camunda.bpm.engine.OptimisticLockingException
Package
Description
Public API of the Camunda Platform engine.
Typical usage of the API starts by the creation of a
Through the services obtained from such a
Typical usage of the API starts by the creation of a
ProcessEngineConfiguration
(typically based on a configuration file), from which a ProcessEngine
can be obtained.Through the services obtained from such a
ProcessEngine
, BPM and workflow operation
can be executed:RepositoryService
:
Manages Deployment
sRuntimeService
:
For starting and searching ProcessInstance
sTaskService
:
Exposes operations to manage human (standalone) Task
s,
such as claiming, completing and assigning tasksIdentityService
:
Used for managing User
s,
Group
s and the relations between themManagementService
:
Exposes engine admin and maintenance operations,
which have no relation to the runtime execution of business processesHistoryService
:
Exposes information about ongoing and past process instances.FormService
:
Access to form data and rendered forms for starting new process instances and completing tasks.-
Uses of OptimisticLockingException in org.camunda.bpm.engine
Modifier and TypeClassDescriptionclass
Exception that is thrown when an optimistic locking error occurs in CockroachDB, caused by concurrent access to the same data entries by multiple transactions. -
Uses of OptimisticLockingException in org.camunda.bpm.engine.impl.cmd
Modifier and TypeMethodDescriptionvoid
CommandLogger.debugCaughtOptimisticLockingException
(OptimisticLockingException e) -
Uses of OptimisticLockingException in org.camunda.bpm.engine.impl.db
Modifier and TypeMethodDescriptionEnginePersistenceLogger.concurrentUpdateDbEntityException
(DbOperation operation) -
Uses of OptimisticLockingException in org.camunda.bpm.qa.upgrade.util
Modifier and TypeFieldDescriptionprotected OptimisticLockingException
CompleteTaskThread.exception