Yes, we have a suite of services that have 2-3 endpoints started per host process. We’ve seen this happen randomly (but fairly consistently) in most of these services. The other strange thing is that we can’t seem to reproduce it with a debugger attached. If we run the services locally, with no debugger and LearningPersistence it happens every subsequent Saga invocation i.e. it only works the first time.
The Sagas are SqlSagas.
The Handler only handles the 1 command message type.
Another assumption I have is that the Assembly scanner is to exclude handlers, should we be using to exclude message types as well? Could this be an issue of endpoints having their “wires crossed” on the Reply?
Our general configuration is RabbitMQ, SqlPersistence (MsSqlServer), Ninject, Outbox, JsonSerialization with a TopShelf Host.