Re: getting WSAECONNABORTED on recv() on Windows XP installations




Thanks for your response. I agree it could be a peer side problem just as
readily as a client problem/. I don't really have easy access to the server
network code - it is a java servlet running under JBoss/Tomcat that, I'm
pretty certain, just uses the standard Java ServerSocket() class in its
implementation.

In any event, the frequency of the problem is OS version dependent:

Win 2K - occurs very, very rarely
Win XP sp1 - occurs more often
Win XP sp2 - occurs much more often (sorry, forgot to mention this in
original post).

Are there any network parameters (timeouts and such) that might have changed
between these 3 versions of the Windows?

"Arkady Frenkel" wrote:

> Check if server on peer listening and on connection and have established
> state for return socket , seems like peer side ( host ) fail
> Arkady
>
> "Curtis" <Curtis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:AC6070F3-9302-4DB9-B056-B0C8223AE97B@xxxxxxxxxxxxxxxx
> >I have a basic networking application that makes HTTP requests via a
> >blocking
> > Winsock socket. It is working fine on all Win 9x and Win 2000 platforms
> > and
> > most Windows XP installations. I've found that all machines will
> > occasionally
> > fail on recv() with a WSAECONNABORTED error so I've included retry logic
> > that
> > closes the socket out and re-starts with a freshly initialized socket. On
> > some Windows XP boxes, most calls succeed but some will continue to fail
> > on
> > multiple retries. In this case, this client is communicating with a
> > JBOSS-based server running on the same computer.
> >
> > My suspicion is that there is a problem with the Windows loopback adapter
> > (or whatever it is called it in XP), but I have not been able to find a
> > way
> > to debug it or work around it.
> >
> > The code basically is:
> >
> > 1. Create, initialize, & connect with a blocking socket
> > 2. send 1 or more send() calls to the socket (about 1K bytes total)
> > 3. call shutdown( hSocket, SD_SEND)
> > 4. call recv() with an 8K buffer
> > 5. socket (sometimes) works fine, sometimes returns WSAECONNABORTED
> >
> > Any thoughts, help or advice would be appreciated!
> >
>
>
>
.


Quantcast