Uncaught exception in C# client library


#1

Having had a stream up and running for the last week or so, in the last half hour, the following exception has been thrown twice (with application restart in between).

\DatasiftStream\DatasiftStream.cs, Line 190: count = resStream.Read(buf, 0, buf.Length);

Full exception message:

System.IO.IOException was unhandled
Message=Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Source=System
StackTrace:
at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at Datasift.DatasiftStream.DatasiftStream.StartStreaming() in C:\Projects\Datasift\DatasiftStream\DatasiftStream.cs:line 190
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException: System.Net.Sockets.SocketException
Message=An existing connection was forcibly closed by the remote host
Source=System
ErrorCode=10054
NativeErrorCode=10054
StackTrace:
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)

The code catches WebExceptions, but this is an IOException so will go uncaught (There should also be a ‘last resort’ catch for any Exception).

P.S. The allowed tags listed for these posts are getting removed. Using “&lt!–break–>” as advised does not work either.


#2

This has been forwarded on to our C# Library developer for review. We will update this thread when we know more.


#3

This has been fixed, and the changes pushed to our GitHub page


#4

Thanks. I’ll check it out