G
Guest
Guest
Archived from groups: microsoft.public.windowsnt.protocol.tcpip (More info?)
I have a multi-threaded application where each child thread owns a socket
and communicates to the net. If I "SuspendThread" these threads while
they're in the midst of a "recv" call, all network access on the PC stops.
If I then "ResumeThread" the threads, network access is restored. When I say
all, I mean all. Streaming audio quites, pings stop working, RD stops
working. IE can no longer connect to web sites.
It doesn't happen to all of my users but, it does happen to some. I can't
reproduce it on my PC but, I'd guess 5% of my users see this. They all seem
to be running XP. Some are SP2 and some are not. Some use third party
firewalls, some do not.
My theory is that I'm suspending a thread when it's in some state where it's
holding a lock that prevents all other TCP access from working on the PC.
I have a multi-threaded application where each child thread owns a socket
and communicates to the net. If I "SuspendThread" these threads while
they're in the midst of a "recv" call, all network access on the PC stops.
If I then "ResumeThread" the threads, network access is restored. When I say
all, I mean all. Streaming audio quites, pings stop working, RD stops
working. IE can no longer connect to web sites.
It doesn't happen to all of my users but, it does happen to some. I can't
reproduce it on my PC but, I'd guess 5% of my users see this. They all seem
to be running XP. Some are SP2 and some are not. Some use third party
firewalls, some do not.
My theory is that I'm suspending a thread when it's in some state where it's
holding a lock that prevents all other TCP access from working on the PC.