You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
We just migrated from SimpleTcp to SuperSimpleTcp and as a result a bunch of unit tests started to fail.
They fail because we're trying to bind to a socket which is already used.
System.Net.Sockets.SocketException : Only one usage of each socket address (protocol/network address/port) is normally permitted.
at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at SuperSimpleTcp.SimpleTcpServer.Start()
I can workaround the problem by adding server.Stop() to the Dispose method.
I wonder why this is not done implicitly by your library. Doesn't this leave sockets open when user software starts a server, and disposes the instance and close the app? Wouldn't you expect that when a server instance is disposed it cleans up everything it used?
The text was updated successfully, but these errors were encountered:
Hi,
We just migrated from SimpleTcp to SuperSimpleTcp and as a result a bunch of unit tests started to fail.
They fail because we're trying to bind to a socket which is already used.
I can workaround the problem by adding
server.Stop()
to theDispose
method.I wonder why this is not done implicitly by your library. Doesn't this leave sockets open when user software starts a server, and disposes the instance and close the app? Wouldn't you expect that when a server instance is disposed it cleans up everything it used?
The text was updated successfully, but these errors were encountered: