wework / grabbit

A lightweight transactional message bus on top of RabbitMQ
Apache License 2.0
98 stars 20 forks source link

The target service was not resolved properly in SagaInvocation #195

Closed rhinof closed 5 years ago

rhinof commented 5 years ago

The value was not resolved properly and instead of resolving the value from the service the message is targeting it resolved it from the routing key the message was sent to. resulting in the SagaCorrelationID always being set to the same value of the SagaID related issue: Wrong started by saga identifier value was set when creating a new saga