Getting a lot of 10060 socket errors with SuperSocket

Apr 2, 2014 at 5:04 AM
Edited Apr 2, 2014 at 6:07 AM
Hi,

I've been monitoring one of our services that uses SuperSocket and I noticed that it has been getting alot of these exceptions lately:
4/2/2014 4:42:14 AM : Session: 45bc99de-5f91-446c-b200-2d607dc83a91/ip:port
Unexpected socket error: 10060
Exception: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
StackTrace: 
4/2/2014 4:42:14 AM : Session: 45bc99de-5f91-446c-b200-2d607dc83a91/ip:port
This session was closed for ClientClosing!
I'm unsure why this happens and on which command it could happen or if this could be in SuperSocket itself.

I've added try-catch blocks to all of my endpoint calls that communicate with remote endpoints. However, it looks like that the catch block doesn't get called (the endpoint calls are in my server's commands). So it looks like the exceptions are getting thrown not from my endpoint calls in my commands but from somewhere else.
Coordinator
Apr 2, 2014 at 8:43 AM
Which version of SuperSocket are you using?
Apr 2, 2014 at 9:30 AM
I believe we're using 1.5.1
Coordinator
Apr 2, 2014 at 3:40 PM
I suggest you to upgrade to latest version of SuperSocket, 1.5.4 or 1.6.1.