This repository was archived by the owner on Oct 22, 2020. It is now read-only.
Calling close on a socket with a broken connection throws an exception (unknown socket id) #18
Description
What steps will reproduce the problem?
1. Purposefully break a connection
2. Call close on the socket
What is the expected output? What do you see instead?
I would assume as long as the socket object is non-null, that calling Close on
it should be a safe operation.
What version of the product are you using? On what operating system?
0.9.0.0, running on Windows 2008 R2 SP1
Please provide any additional information below.
Right now, I am having to wrap my Close in a try/catch, ignoring any
Udt.SocketException that happen. Is there a different, recommended way to do
this?
Original issue reported on code.google.com by [email protected] on 14 Nov 2013 at 6:51