
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-28-2017 09:12 AM
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
- Labels:
-
Alfresco Process Services

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-29-2017 07:58 AM
After a lot of debugging I discovered that Activiti's command context was being manipulated in my code, which was causing the random behavior.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-28-2017 09:20 AM
Also, I'm using activiti-spring-boot-starter-basic

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-29-2017 07:58 AM
After a lot of debugging I discovered that Activiti's command context was being manipulated in my code, which was causing the random behavior.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2021 04:34 AM
HI , buddy ,recently i have same problem with you , i was wondering could you share your method how to solve this random behaviour ??
