We have a requirement to create highly available subscriber endpoints that utilize the MSMQ transport. We’ve done this well in the command sending scenario using an instance mapping file and a custom distribution strategy that checks that a particular endpoint instance’s Windows Service is running before sending it a message. However, that mechanism isn’t available (as we’ve experienced) when a publisher sends a message to a particular subscriber since the subscriptions specify physical endpoint instances, and not just logical endpoints. Also, the autosubscribe behavior of the subscriber always sends the subscription request pointing back to the physical endpoint instance that sent it, not a logical endpoint.
Are we possibly missing something, or is this functionality not supported?
If not supported, what is particular’s recommendation on supporting highly available scaled out subscriber endpoints with MSMQ?