I'm creating a process instance as such:
processInstance = runtimeService.startProcessInstanceByKeyAndTenantId(key, initialParameters, tenantId + (isTest ? TEST_TENANT_SUFFIX : PRODUCTION_TENANT_SUFFIX));
which always returns a processInstance, but sometimes(seemingly randomly) the returned process instance does not exist in the database:
historyService.createHistoricProcessInstanceQuery().processInstanceId(processInstance.getId()).singleResult() == null
runtimeService.createProcessInstanceQuery().processInstanceId(processInstance.getId()).singleResult() == null
I've also logged the mariadb queries and I've noticed that the times that the instance does not exist; no insert queries are logged in the database, so the process instance was not inserted and then deleted.
these problems started appearing after migrating to activiti6
Solved! Go to Solution.
After a lot of debugging I discovered that Activiti's command context was being manipulated in my code, which was causing the random behavior.
Also, I'm using activiti-spring-boot-starter-basic
After a lot of debugging I discovered that Activiti's command context was being manipulated in my code, which was causing the random behavior.
HI , buddy ,recently i have same problem with you , i was wondering could you share your method how to solve this random behaviour ??
Ask for and offer help to other Alfresco Process Services and Activiti Users and members of the Alfresco team.
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.