Commands can't be dispatched to TaskAggregate if originated from a runinng UnitOfWork which has state COMMITED - Githubissues

holunda-io / camunda-bpm-taskpool

Library for pooling user tasks and process related business objects.

https://www.holunda.io/camunda-bpm-taskpool/

Apache License 2.0

68 stars 26 forks source link

Commands can't be dispatched to TaskAggregate if originated from a runinng UnitOfWork which has state COMMITED #708

Closed zambrovski closed 1 year ago

zambrovski commented 1 year ago

See: https://discuss.axoniq.io/t/understanding-unitofwork/4571

The setup is:

Polyflow Core (command model) an Camunda Collector in one deployment
send in transaction switch doesn't matter
Camunda Collector is sending commands in TxAwareAccumulatingEngineTaskCommandSender - this is performed before/after commit.

Both cases don't work:

The original command is received via Axon Command dispatch, triggers Camunda change, dispatches commands -> can't emit events in aggregate (because root UoW is in wrong state)
The original change is triggering an Interaction Event, which is caught by tracking processor (inside the Camunda Engine Client), triggers Camunda change, dispatches commands -> can't emit events in aggregate (because root UoW is in wrong state)

zambrovski commented 1 year ago

a workaround is found by #714