B
Bhavesh Shah
I am having an issue with WCF and clustered MSMQ and hoping someone could
help me here.
I have a Service with MSMQ binding hosted in IIS 7 using WAS listing to a
cluster MSMQ. Everything works fine, when I start my server/service.
Messages come into system and service receives it and processes it.
Now, active server in cluster dies and it fails over to second server.
After failover,
no new messages will be processed until I restart the IIS or WAS.
I do not see any errors in Event Log or Trace. Everything seems to be
working as normal. WAS is able receive messages from both servers.
I created a console host and I was able to catch a Service Host exception
and restart the host after failover. During Failover, the Service Host is
not able to query MSMQ and throws a MSMQ missing exception.
Does anyone know how to catch Service Host Faulted exception in WAS process?
Thanks for your help
help me here.
I have a Service with MSMQ binding hosted in IIS 7 using WAS listing to a
cluster MSMQ. Everything works fine, when I start my server/service.
Messages come into system and service receives it and processes it.
Now, active server in cluster dies and it fails over to second server.
After failover,
no new messages will be processed until I restart the IIS or WAS.
I do not see any errors in Event Log or Trace. Everything seems to be
working as normal. WAS is able receive messages from both servers.
I created a console host and I was able to catch a Service Host exception
and restart the host after failover. During Failover, the Service Host is
not able to query MSMQ and throws a MSMQ missing exception.
Does anyone know how to catch Service Host Faulted exception in WAS process?
Thanks for your help