Hello,
We have an on-premise installation of Windows Service Bus 1.1 with a three node farm. The actual communication to the service bus is done through a WCF Service with NetMessagingBinding.
When communicating to service bus with something like a QueueClient, we have the option to declare a connection string that contains an endpoint with addresses to all three instances running in the farm (which I'm assuming is how load-balancing\high availability is maintained). But I don't see that same ability when using NetMessagingBinding. It appears I can only include one of the three instances as the endpoint.
Does this mean that if I only specify one endpoint uri, we lose we lose load-balancing? So if that one node goes out, all communication stops?
Is there a way to specify all three endpoints and accommodate service bus load-balancing when using NetMessagingBinding? Or am I missing something all together?
Thanks!
We have an on-premise installation of Windows Service Bus 1.1 with a three node farm. The actual communication to the service bus is done through a WCF Service with NetMessagingBinding.
When communicating to service bus with something like a QueueClient, we have the option to declare a connection string that contains an endpoint with addresses to all three instances running in the farm (which I'm assuming is how load-balancing\high availability is maintained). But I don't see that same ability when using NetMessagingBinding. It appears I can only include one of the three instances as the endpoint.
Does this mean that if I only specify one endpoint uri, we lose we lose load-balancing? So if that one node goes out, all communication stops?
Is there a way to specify all three endpoints and accommodate service bus load-balancing when using NetMessagingBinding? Or am I missing something all together?
Thanks!
John