[Mono-dev] WCF Fail with System.Net.Sockets.SocketException: Connection reset by peer
robwilkens at gmail.com
Mon Jul 9 14:32:50 UTC 2012
Just want to update the list in case anyone was following…
I was able to reproduce some of the problems, and came up with some work arounds that wouldn't crash the WCF server on client disconnect (windows doesn't crash the server), at least for the issues i was able to reproduce. I tried to keep the fixes confined so they have minimal impact on things which were unrelated, for example, i catch the exceptions where they were causing failures, but where they were not causing failures, in general i tried to let the exception flow through so it could be caught by something more appropriate, such as the user program itself.
The person who reported them originally is going to try these changes on a live server over the next few days to see if it helps matters. They are in a pull request, but i am not in a hurry for them to be pulled, because among other things, i don't generally use WCF and these issue don't affect me. They were just interesting to me.
I have personal issues (it's not me who is having the problem, but i need to deal with it), unrelated to mono, which have been holding me up from trying to do more work with mono the last several days. I don't want to get into them here. Depending on how things go, i might not touch mono source again until some time next month. Please don't take this as a lack of interest from me -- I've very much enjoyed being active here, both learning and contributing (when i do it right). Will try to keep up with the mailing list during this time, and if a problem really interests me, i might find time to get involved.
On Jun 29, 2012, at 6:15 AM, Robert Wilkens wrote:
> Thanks - I'm on my mac now and trying to set up mono develop.. It appears to have an easier time with the alpha version of mono, but then it said 'update available' and downloaded an older version then stopped working again, I'll get it soon. Otherwise, I'll be on my linux laptop soon, just wanted to set up a second machine to test on since networking code sometimes works better when it's not just localhost to localhost.
> On Jun 28, 2012, at 6:35 PM, shahbour wrote:
>> Hello Rob
>> I am attaching a simple application to demonstrate the error we are getting.
>> Unfortunately using the above example the server is not crashing but still
>> it raise the error (note that in my live app , some time it do the same but
>> crash more)
>> If you run the server like below you will notice the error
>> mono --debug --trace=N:nothing TestWCFServer.exe
>> Press enter to exit
>> [0xb0a7d000:] EXCEPTION handling: System.Net.Sockets.SocketException:
>> Connection reset by peer
>> [0xb0a7d000:] EXCEPTION handling: System.IO.IOException: EndRead failure
>> To run the example just start the server , then start the client and before
>> getting the result back from server close it (Ctrl+C)
>> I put a delay in the server to demonstrate the request over internet and to
>> have time to close it. After you close it by small time the application will
>> raise the above error .
>> Tomorrow I will change the client to a silver light application to simulate
>> exactly my application because the server crash approximately every time I
>> close the browser before getting the result in my live example.
>> View this message in context: http://mono.1490590.n4.nabble.com/WCF-Fail-with-System-Net-Sockets-SocketException-Connection-reset-by-peer-tp4650173p4650235.html
>> Sent from the Mono - Dev mailing list archive at Nabble.com.
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list