I have a WCF service using one-way net.msmq transport to deliver messages to a high availability cluster.
I have followed a few articles I have found on setting up WCF in a cluster environment and essnetially have the following queues
Node A: private$\MI/ManagementInformationService.svc
Node B: private$\MI/ManagementInformationService.svc
Although I am not sure why I need the local queues.
I've installed the WCF application into IIS7 on Node A and Node B. I;ve configured both nodes to the following address:
So, I configure my Web Servers to deliver the MI to the clustered endpoing via WCF net.msmq binding.
At this point, everything works and as messages hit the clustered queue, they are picked up by one of the nodes and processed. However, when I fail over the cluster, the second node does not automatically spring into life, as I would expect it to with WAS.
However, if I browse the WSDL for my service on the now-current node, then it does indeed spring into life and process the messages off the queue.
So I turn on WCF tracing, IISReset fire up the WSDL, IISReset (to flush the WCF Trace log) then see the following:
A warning: Cannot detec
View Complete Post