I started porting the main process of an application to run on camunda some weeks ago.
Until now the process was hardcoded in the application. In the past there where so problems with transaction scopes and optimistic locking exceptions.
The main reason to switch to the camunda process engine was to make it easier to handle such error conditions within the BPMN process.
But now, during the development and testing the process I have seen for my opinion way to many Optimistic-Locking-Exceptions, Deadlocks, Foreign-Key-Violations and so on IN the the camunda process engine (additionally with cryptic error messages).
Did I miss some kind of magic switch to avoid these problems?
Yes, the process is running two parallel branches and a sub process, but I expected the engine could handle these without crashing.