-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
7.2.0, 7.1.0, 7.3.0
Scenario:
A process with a single manual task (user task, i.e. wait state, as well) that is async after and parallel multi instance (e.g. 3 instances).
Starting such a process results in integrity constraint violations a la
### The error may involve org.camunda.bpm.engine.impl.persistence.entity.ExecutionEntity.insertExecution-Inline ### The error occurred while setting parameters ### SQL: insert into ACT_RU_EXECUTION ( ID_, PROC_INST_ID_, BUSINESS_KEY_, PROC_DEF_ID_, ACT_ID_, ACT_INST_ID_, IS_ACTIVE_, IS_CONCURRENT_, IS_SCOPE_, IS_EVENT_SCOPE_, PARENT_ID_, SUPER_EXEC_, SUPER_CASE_EXEC_, CASE_INST_ID_, SUSPENSION_STATE_, CACHED_ENT_STATE_, REV_ ) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 1 ) ### Cause: org.h2.jdbc.JdbcSQLException: Referentielle Integrität verletzt: "ACT_FK_EXE_PARENT: PUBLIC.ACT_RU_EXECUTION FOREIGN KEY(PARENT_ID_) REFERENCES PUBLIC.ACT_RU_EXECUTION(ID_) ('103')"
and from a quick look at the flush summary, it appears that the engine attempts to create four jobs, probably one for the scope execution and one for each mi instance.
Should work on 7.3.
This is the controller panel for Smart Panels app
- is related to
-
CAM-3826 Write migration tests for job definitions/job execution for async MI tasks
- Closed