Hey,
Hope I didn't miss it on the net. My architecture contains several services (physically located on different systems) communicating via WCF.
What is the best way to detect network errors
I've thought about two possibilities -
1. register for the Faulted event on the channel - This does not seem to work as I excepted. Channel doesn't necessary go to faulted state when a network error occurs. why is that
2. I can use events from System.Net and Microsoft.VisualBasic.Devices - but I prefer to think that WCF has that mechanism inside (that is - detect network errors, detect network availability, etc.).
Thanks, Dan.
Network error detection, handling and best practices
Shiva Manjunath
From the blob:
"Reliable sessions also track the connection liveliness and let you free resources on the server side if the client “goes away” for longer than a given amount of time"
How do I achive that
Can you post a sample
bennettdan
How does RM "minimize this"
As far as I read so far, RM makes sure messages are received in the order they were sent, and prevents lost message by trying to send them more than once.
1) If there was a network problem, will RM renew the client-service connection
2) The sender of the message (client or service) receives an error when trying to send a message - what about the other side
3) Is there a way for the service to know a client is not connected anymore, due to network error
Chewmp
There is a sample in the SDK that you may want to look at:
WS Reliable Session Sample
The 'livliness' he was talking about I think refers to the acknowledgementInterval and/or the inactivityTimeout attributes in the reliableSession element.
Thanks!
Scott
Christian Norager
Let me clarify....
If there is a network glitch which somehow causes the message to be lost, RM will recover and resend the message, so that the effects of the glitch will be minimized. Obviously if the network is completely down, then that won't be much help.
Please see this for additional data:
http://blogs.msdn.com/shycohen/archive/2006/02/20/535717.aspx
Thanks!
Scott
jaczura
If you already have a channel open and the network has a problem, then you won't know about it until you actually try and use it. If this happens then it will throw an error. You can minimize this by using RM:
http://windowssdk.msdn.microsoft.com/library/default.asp url=/library/en-us/wcf_con/html/a7fc4146-ee2c-444c-82d4-ef6faffccc2d.asp