Now my program does not produce the error. A thread that was involved in the
process failed with the effect of blocking the main thread that processed
the socket input and produced the output. That ended up in this strange
error after waiting half a second (more or less). instead of being catched
b
I am having the similar problem when running TCP server application on windows
XP. The server can only reads once from the handle of socket, then any
operation on the handle will cause error because it is already finalized. It
seems a platform issues but I have no idea about it.
Date: Tue,
