An update on this -
I believe this has nothing to do with the messaging or saga semantics and more to do with the the ObjectBuilder. Brought up here previously.
Each endpoint instance (2 in the same host) has a Child Kernel that still has a reference to the root kernel but I don’t see how any modifications the Child Kernel could affect the Parent Kernel.
The Saga just won’t initiate the insert, nothing gets sent over the wire. It has an open connection to do so.
Again, this is only an issue for all subsequent requests. The first one works as expected.
Removing the NinjectBuilder and moving to a ServiceLocator pattern within the handlers resolves the issue. This is obviously not ideal and changing containers is not an option.
I haven’t gotten as far the why and would really appreciate some basic things to try to get this working. We’re finalizing a licensing agreement with Particular as this is our initial implementation and this has already created some doubts in our organization.
I hope this new info can lead to a little more activity on this post.