Re: Software Caused Connection Abort (10053) on Client

Unfortunately this is on a server machine, Windows 2003 Server. Which
makes me kind of suspect the VMWare stack of agents. On the server I
have already checked out the backlog setting as well as the
SynAttackProtect feature added into Windows 2003 Server starting with
SP1. None of these seem to be issues. 

-----Original Message-----
From: Gregg Wonderly [mailto:[email protected]] 
Sent: Sunday, November 20, 2005 8:49 AM
To: Robert DiFalco
Cc: [email protected]
Subject: Re: Software Caused Connection Abort (10053) on Client

Robert DiFalco wrote:
> Any ideas appreciated. And remember this is intermittent and it only 
> seems to happen with Windows Servers. If I use Linux or Solaris as a 
> server we do not get this intermittent issue.

This is a known behavior in the windows stack.  Anytime that there are
too many sockets opened based on the limit built into the OS, it will
respond to new connection requests with RST, instead of just ignoring
the SYN packet.  This results, of course, in software that is trying to
connect, to abort with errors that are more commonly associated with
stream failures, not connection timeouts.

The win9x family has very small limits on total open sockets.  Windows
XP still, apparently has a limit, although it is much higher.  But, you
have to use the full blown server versions to get unlimited sockets it
appears.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html