#10 Fatal thread exit in WebResponder

bug
open
nobody
5
2013-01-29
2011-06-25
Bob Denny
No

If the other end closes its socket while the WebResponder is sending, it can cause an IOException.

[2011-06-23T19:14:21] *** FATAL EXCEPTION ***
[2011-06-23T19:14:21] System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at com.dc3.cwcom.WebResponder.ProcessRequest()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
[2011-06-23T19:14:21] ***********************

This should be caught and result in cleanup of the connection.

Discussion


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks