|
-
January 17th, 2012, 02:02 AM
#4
Re: Winsock fails after 1 hour
 Originally Posted by softmessager
...
Problem:
After exactly 1 hour, my client closes with the socket error param code = 10053
My server too errors out at the following line
result = WaitForMultipleObjects(object_count,wait_objects,FALSE,210000);
Well, this "code snippet" doesn't help us to understand which (exactly!) line of your code causes the error 10053.
And FYI, MSDN description of this error is
WSAECONNABORTED
10053
Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
So at this place I agree with Paul:
 Originally Posted by Paul McKenzie
Unless we have your program and source code, there is no way anyone can answer your question with anything but guessing
Victor Nijegorodov
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|