NServiceBus pipeline with Distributors

Answer 1

If I were you, I would reconsider my design and look into something more along the lines of the application described in the MSDN Magazine article: A Peer-To-Peer Work Processing App With WCF.

One of the things that I love about NServiceBus is its simplicity. It isn't one-size-fits-all for asynchronous messaging. The way it's been designed really forces you to consider coupling too. When I find myself asking questions similar to yours then it's usually an indication that I'm not thinking about my design the best way.

If you don't already own it, you might also consider purchasing the book "Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions." There are several patterns discussed in it that might help with what you're doing.

Answer 2

The problem you have is that your nodes don't see each others list of subscribers. The reason you're having that problem is that your trying out a production scenario (scale-out) under the default NServiceBus profile (lite) which doesn't support scale-out but makes single-machine development very productive.

To solve the problem, run the NServiceBus host using the production profile as described on this page:

http://www.nservicebus.com/Profiles.aspx

That will let different nodes share the same list of subscribers.

Other than that, your configuration is right on.