Jan 9, 2013 at 10:15 PM
Edited Jan 10, 2013 at 2:20 AM
Thank you for your concern.
Lastly I have one more question.
Is the [id #12392] issue on the issue tracker resolved? (TcpAsyncSocketListener stop on "An existing connection was forcibly closed by the remote host")
Actually, I have got this error message in supersocket err.log, and the server started to refuse all the incoming connections after the error occurred.
I compared the TcpAsyncSocketListener.ProcessAccept source of 1.5 beta version source with stable version, but it was same exactly, so I doubt that you did not fix this error to stable version.
Please answer to this question and happy new year Kerry!