Hi! Can you explain what do you mean by static variables in delegate class? Are there any restrictions on static variables while working with camunda?
I have the same problem (but in postgreSQL) and I don’t know what to do with this.
I have a lot of places where variables that are already existed in camunda process are set again but usually I don’t have any problem with this, they’re just rewritten. But now I have this error and I don’t understand why.
The baseline is: Any code that is called by the process engine must be thread-safe. If your classes use mutable static variables, this is not the case. In particular, if you hold instances of engine-managed objects (e.g. Execution, Task, etc.) in static variables, you get funny behavior.
One more point though: This particular constraint is violated whenever the same variable is created in the same scope (=> execution or task) twice in parallel. The second transaction will fail with this exception. Could this be the case here?
I’ve tried to reproduce it in tests but I couldn’t. So I’ve just tried to rename this variable and it has worked! Then I renamed it back and the problem didn’t return. It was very strange until I’ve realized that there was one more thing that I’ve changed: I’ve deleted this code: execution.removeVariable("sa_absent_ngris_uuid");
Which I’ve added in an attempt to resolve this issue. So it seems that initial problem was caused by something else but this code made it persistent.
Anyway for now the problem is resolved.