Hi folks
We have a production system using Camunda ver. 7.2.0 (as spring application) running on Linux JBoss 6.4 cluster with two nodes running for a bit more than one year. There is nothing out of the ordinary in terms of the setup. No default setup were modified.
// Default to generic workflow if variable map is empty
if (null == workflowVariableMap) {
workflowVariableMap = populateGenricWorkflowVaribaleMap(application);
runtimeService.startProcessInstanceByKey(processKey, workflowVariableMap);
} else {
// start the workflow with the assigned process key
runtimeService.startProcessInstanceByKey(processKey, workflowVariableMap);
}
We have been noticing (only in Production) that process instances are not getting created for around 5% of the applications. Other application data is persisted however there is no workflow instance including in Camunda history tables. I am thinking that they Camunda failed to get executed.
My questions are
- Have anyone faced similar problems?
- If so, what was going wrong?
- Could this be a thread pool issue? I read somewhere in the forum that there is only upto 3 threads in the job acquisition pool. But what about job executer thread? Does it have a threashold on no. of applications that it can handle concurrently?
- Are there any settings that I can override?
I do apologise if I asked a lot. But I am trying to get your thinking around all probable issues that can lead to this issue.
Regards
Prad