Open martinmine opened 3 years ago
I found some interesting logs. I will investigate them.
Cool, looking forward to see what you find out. Let me know if you need any more info.
There are two interesting issues:
1) 10052 error of UDP; 2) the unhandled exception in the method PipeChannel.Run;
Did you find any other exceptions which might be related with the second issue?
I have looked over a few more logs and haven't seen anything. I have looked a bit on the PipeChannel
class and I don't see how we can enter HandleClosing()
before Start()
has been executed. Might be something that calls a Close
or Detach
method before Start
has been executed?
I have been running SuperSocket 2.0 in production now for soon a week and it seems to run buttery smooth. My logfiles do however show that there are a few things that is a bit off. When connections are closed it might be that we get some socket exceptions. Specifically 10052, 10053, 10054, and 10060:
(these are just examples, I can get for example 463 instances of error 10060 in the past 24 hours)
I am aware that I can configure the logging framework to not log events like these but it seems rather odd. It would be really great if these scenarios where the client might for example not complete the final handshake completely that we don't get error events and our log files are not filled up with noise.