We send a "CompleteCommand" to an axon CommandHandler. This command contains data that should end up in the process.
We use the polyflow taskpool-job-handler and have the camunda.bpm.eventing.task=false property disabled.
Problem
What we see: In a process with many user tasks that are all completed via taskService.complateTask(cmd.id, cmd.variables()) one (the first) task is completed, but the TaskCompletedEngineEvent does not contain the passed variables.
In the cockpit (and follow-up TaskCreatedEngineEvents) the variables. exist.
Note: This is a user task that receives (large) bytes arrays containing base64 images.
Theory: Is it possible, that the async taskpool-job tries to read the process-variables while they are still "locked" by the camunda transaction?
Setup:
camunda 7.18.4, poylflow 3.8.1
We send a "CompleteCommand" to an axon CommandHandler. This command contains data that should end up in the process. We use the polyflow
taskpool-job-handler
and have thecamunda.bpm.eventing.task=false
property disabled.Problem
What we see: In a process with many user tasks that are all completed via
taskService.complateTask(cmd.id, cmd.variables())
one (the first) task is completed, but theTaskCompletedEngineEvent
does not contain the passed variables. In the cockpit (and follow-upTaskCreatedEngineEvent
s) the variables. exist.Note: This is a user task that receives (large) bytes arrays containing base64 images.
Theory: Is it possible, that the async taskpool-job tries to read the process-variables while they are still "locked" by the camunda transaction?