Exception while closing command context (How skip task ending)

Camunda 7 Topics Discussion & Questions
5

Hi @neki,

I suspect the problem is related to how process execution is mapped to transactions.

  1. When you execute an instance of the example process you provided above, it’s actually executed in a single transaction and once the Process Instance is finished, the related data is committed to the database.
  2. If you decide to delete this Process Instance, this call will be executed in a transaction concurrent to the first one. The call won’t be able to find the Process Instance in the database since it hasn’t been committed yet, resulting in an NPE.

I agree that getting an NPE is not really descriptive, but it’s actually an expected behavior.

What you can do, as a workaround, is to introduce a transaction barrier on the Start event of the process, through an asynBefore or asynAfter flag. This will create the Process Instance in one transaction (and commit it to the database), and continue with its execution in a second transaction after the commit (through a Job). If a delete call is executed during the process execution, the Process Instance ID will already be present in the database now.

Does this solve your problem?

Best,
Nikola

1 Like