Hi @wwitt ,
Thanks for the feedback.
- So you mean the deadlock exception that I have been observing is infact “Optimistic Lock Exception” which should rollback the transaction to previous wait state. But then when I try to resume it using
runtimeService.activateProcessInstanceById(processInstanceId);
I get :
Cannot set suspension state ‘active’ for ProcessInstance[91ec38f0-59c8-11ea-bbf7-0050568e1cce]': already in state ‘active’.
Doesn’t that mean the execution was completed . So , I believe deadlock exception is not the optimistic Lock Exception that I am looking for. Right ?
- Similarly , when I try to cancel a running process by using
runtimeService.deleteProcessInstance(processInstanceId, “cancelled - By - User”);
It sill throws me similar exception all the time
{
“timestamp”: “2020-02-28T01:15:54.084+0000”,
“status”: 500,
“error”: “Internal Server Error”,
“message”: “Execution[ id ‘ccdb7646-59c7-11ea-bbf7-0050568e1cce’ ] - activity ‘XXXXX’ - parent ‘ccdb4f2d-59c7-11ea-bbf7-0050568e1cce’ was updated by another transaction concurrently”,
“path”: “/flow-orchestrator/process/cancel-process”
}
Not sure what I am doing wrong here .
Thanks.