Uses of Class
Packages that use OptimisticLockingException Package Description org.camunda.bpm.enginePublic API of the Camunda Platform engine.
Typical usage of the API starts by the creation of a
ProcessEngineConfiguration(typically based on a configuration file), from which a
ProcessEnginecan be obtained.
Through the services obtained from such a
ProcessEngine, BPM and workflow operation can be executed:
RuntimeService: For starting and searching
TaskService: Exposes operations to manage human (standalone)
Tasks, such as claiming, completing and assigning tasks
IdentityService: Used for managing
Groups and the relations between them
ManagementService: Exposes engine admin and maintenance operations, which have no relation to the runtime execution of business processes
HistoryService: Exposes information about ongoing and past process instances.
FormService: Access to form data and rendered forms for starting new process instances and completing tasks.
org.camunda.bpm.engine.impl.cmd org.camunda.bpm.engine.impl.db org.camunda.bpm.qa.upgrade.util
Uses of OptimisticLockingException in org.camunda.bpm.engine
Subclasses of OptimisticLockingException in org.camunda.bpm.engine Modifier and Type Class Description
CrdbTransactionRetryExceptionException that is thrown when an optimistic locking error occurs in CockroachDB, caused by concurrent access to the same data entries by multiple transactions.
Methods in org.camunda.bpm.engine.impl.cmd with parameters of type OptimisticLockingException Modifier and Type Method Description
Methods in org.camunda.bpm.engine.impl.db that return OptimisticLockingException Modifier and Type Method Description
Fields in org.camunda.bpm.qa.upgrade.util declared as OptimisticLockingException Modifier and Type Field Description
Methods in org.camunda.bpm.qa.upgrade.util that return OptimisticLockingException Modifier and Type Method Description