We are currently struggling to understand how access to the Saga is handeld with the Axon tracking event processor.
A small Example:
We currently have multiple Microservices running all connecting to the same event/token/saga store(via jpa). These stores are all currently located in a Mysql DB(Precona XtraDB Cluster).
The metioned Services are all trying to write to the same Saga and this is where we seem to run into a problem.
As soon as one of the services writes the first value into the saga, he claims the tracking token and does not seem to let go afterwards anymore.
It seems like because of that we are currently running into problems accessing the saga from any other Service that is not currenly the owner of the Saga.
Is this expected behavior or is there some configuration we can do to prevent such a case?