Re: ??? error 31008 Component was busy and got dis (General questions)
Rainer,
it's exactly what it says. Everything was well, there were no problems, and suddenly connection was dropped in the middle of the work. I guess winsock would return 'connection reset by peer', but since this isn't winsock error (since no error is provided in FD_CLOSE callback) we return our own.
I can't give better explanation, sorry.
When does it happen? Can you find any pattern for the behavior?
Complete thread:
- ??? error 31008 Component was busy and got disconn - rs4u, 2005-08-03, 08:05
- Re: ??? error 31008 Component was busy and got dis - wodSupport, 2005-08-03, 08:34
- Re: ??? error 31008 Component was busy and got dis - rs4u, 2005-08-03, 08:57
- Re: ??? error 31008 Component was busy and got dis - rs4u, 2005-08-03, 10:03
- Re: ??? error 31008 Component was busy and got dis - wodSupport, 2005-08-03, 19:32
- Re: ??? error 31008 Component was busy and got dis - rs4u, 2005-08-03, 10:03
- Re: ??? error 31008 Component was busy and got dis - rs4u, 2005-08-03, 08:57
- Re: ??? error 31008 Component was busy and got dis - wodSupport, 2005-08-03, 08:34