33541f5e   
   From: barmar@alum.mit.edu   
      
   In article   
   <5bc13cc2-442b-4b55-b78d-1df91bb8da86@g1g2000pra.googlegroups.com>,   
    Bob  wrote:   
      
   > Hello-   
   >   
   > Im working on a multithreaded TCP server.  Im seeing   
   > send() get called to the other end (which is up, running,   
   > and connected) which then seems to 'hang' and never   
   > returns from the send call.  My server is running on   
   > an older 2.4.36 kernel and the client side is on XP.   
   > This happens during my testing when only 1 client is   
   > connected every few hours, sometimes up to a day   
   > before it shows up.   
   >   
   > Before I dive into kernel issues or anything else   
   > I thought Id check here for something obvious.   
   >   
   > Thanks in advance   
      
   Is the receiver reading everything?  Send() will block if the window   
   fills up, which will happen if the reader gets far behind the sender.   
      
   It could also happen if acknowledgements aren't getting back to the   
   sender, so it doesn't see the window updates.   
      
   Run Wireshark and see what's happening.   
      
   --   
   Barry Margolin, barmar@alum.mit.edu   
   Arlington, MA   
   *** PLEASE don't copy me on replies, I'll read them in the group ***   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)