Hello,
After migrating to Camunda 7.22, some BPMNs launch without any problems and others do not. For those who are launching, we have these traces:
DEBUG [||||] org.camunda.bpm.engine.cmd - ENGINE-13005 Starting command -------------------- StartProcessInstanceCmd ----------------------
DEBUG [||||] org.camunda.bpm.engine.cmd - ENGINE-13009 opening new command context
DEBUG [||||] o.c.b.e.i.p.e.P.selectLatestProcessDefinitionByKey - ==> Preparing: select * from ACT_RE_PROCDEF p1 inner join (select KEY_, TENANT_ID_, max(VERSION_) as MAX_VERSION from ACT_RE_PROCDEF RES where KEY_ = ? group by TENANT_ID_, KEY_) p2 on p1.KEY_ = p2.KEY_ where p1.VERSION_ = p2.MAX_VERSION and (p1.TENANT_ID_ = p2.TENANT_ID_ or (p1.TENANT_ID_ is null and p2.TENANT_ID_ is null))
DEBUG [||||] o.c.b.e.i.p.e.P.selectLatestProcessDefinitionByKey - ==> Parameters: mybpmn1(String)
DEBUG [||||] o.c.b.e.i.p.e.P.selectLatestProcessDefinitionByKey - <== Total: 1
DEBUG [||||] org.camunda.bpm.engine.persistence - ENGINE-03031 Initializing execution ‘ProcessInstance[320]’
DEBUG [||||] org.camunda.bpm.engine.persistence - ENGINE-03032 Initializing timer declaration ‘ProcessInstance[320]’
DEBUG [||||] org.camunda.bpm.application - ENGINE-07023 No target process application found for Execution[320], ProcessDefinition[mybpmn1:1:166], Deployment[1] Registrations [ ]
DEBUG [||||] org.camunda.bpm.engine.context - ENGINE-16001 Executing atomic operation org.camunda.bpm.engine.impl.pvm.runtime.operation.PvmAtomicOperationProcessStart@301fb473 on ProcessInstance[320]
However, for the one that doesn’t launch, we don’t see any exceptions logged, but the command is closed quickly without explanation :
DEBUG [||||] org.camunda.bpm.engine.cmd - ENGINE-13005 Starting command -------------------- StartProcessInstanceCmd ----------------------
DEBUG [||||] org.camunda.bpm.engine.cmd - ENGINE-13009 opening new command context
DEBUG [||||] o.c.b.e.i.p.e.P.selectLatestProcessDefinitionByKey - ==> Preparing: select * from ACT_RE_PROCDEF p1 inner join (select KEY_, TENANT_ID_, max(VERSION_) as MAX_VERSION from ACT_RE_PROCDEF RES where KEY_ = ? group by TENANT_ID_, KEY_) p2 on p1.KEY_ = p2.KEY_ where p1.VERSION_ = p2.MAX_VERSION and (p1.TENANT_ID_ = p2.TENANT_ID_ or (p1.TENANT_ID_ is null and p2.TENANT_ID_ is null))
DEBUG [||||] o.c.b.e.i.p.e.P.selectLatestProcessDefinitionByKey - ==> Parameters: myBpmn2(String)
DEBUG [||||] o.c.b.e.i.p.e.P.selectLatestProcessDefinitionByKey - <== Total: 1
DEBUG [||||] org.camunda.bpm.engine.persistence - ENGINE-03031 Initializing execution ‘ProcessInstance[241]’
DEBUG [||||] org.camunda.bpm.engine.persistence - ENGINE-03032 Initializing timer declaration ‘ProcessInstance[241]’
DEBUG [||||] org.camunda.bpm.application - ENGINE-07023 No target process application found for Execution[241], ProcessDefinition[myBpmn2:1:137], Deployment[1] Registrations [ ]
DEBUG [||||] o.c.b.e.i.p.e.J.selectJobDefinition - ==> Preparing: select * from ACT_RU_JOBDEF where ID_ = ?
DEBUG [||||] o.c.b.e.i.p.e.J.selectJobDefinition - ==> Parameters: 138(String)
DEBUG [||||] o.c.b.e.i.p.e.J.selectJobDefinition - <== Total: 1
DEBUG [||||] org.camunda.bpm.engine.cmd - ENGINE-13011 closing existing command context
DEBUG [||||] org.camunda.bpm.engine.persistence - ENGINE-03006 Cache state after flush
we have a line in the table ACT_RU_INCIDENT with status failedJob but no explicit error cause
How we can have more details for this problem ? and what can be ?