Software Caused Connection Abort.   

Sorry, but I'm really stumped and I think I have a Windows issue here.

We have a VMWare stack simulating many agents connecting to a Windows 
server. We are running jobs in batches of 25 agents at a time. When a job is 
sent to an agent, it then calls back to the server to post 
results.Sometimes, some or all of the 25 agents in a batch will fail with 
Software Caused Connection Abort as the agent is trying to WRITE to the 
server.

My initial thought was that the backlog value was too low on the Windows 
Server. However, wouldn't this give me a Connection Refused exception rather 
than a Connection Abort on Write exception?!?

Taking a look at a snoop on the server, what I do notice is that after 
accepting the socket from the agent, the server sends a FIN and then 
immediately afterwards a RST. Normally there is an ACK in between, but in 
this case the FIN doesn't even appear to wait before calling RST. What 
causes this sort of sequence on the server socket?

Could it be the backlog or some dynamic SYN ATTACK detection code that MS 
has slipped into 2003 Server? Any ideas appreciated. And remember this is 
intermittent and it only seems to happen with Windows Servers. NOTE: If I 
use Linux or Solaris as a server we do not get this intermittent issue.

FWIW, this is Java and RMI; however, I don't think that is part of the 
issue. TIA.

(Also, if there is a better forum to post this, let me know)

R.

date: Fri, 18 Nov 2005 17:54:07 -0800   author:   Robert DiFalco am

Re: Software Caused Connection Abort.   

You have to debug server side in connection with client , synchronize times 
with Net.exe ( net time command ) and start some sniffer on the both ends
to log what happen , default backlog of the server is 200 so seems that not 
the issue
Arkady
"Robert DiFalco" <rdifalco@newsgroups.nospam> wrote in message 
news:%23oDgewK7FHA.1416@TK2MSFTNGP09.phx.gbl...
> Sorry, but I'm really stumped and I think I have a Windows issue here.
>
> We have a VMWare stack simulating many agents connecting to a Windows 
> server. We are running jobs in batches of 25 agents at a time. When a job 
> is sent to an agent, it then calls back to the server to post 
> results.Sometimes, some or all of the 25 agents in a batch will fail with 
> Software Caused Connection Abort as the agent is trying to WRITE to the 
> server.
>
> My initial thought was that the backlog value was too low on the Windows 
> Server. However, wouldn't this give me a Connection Refused exception 
> rather than a Connection Abort on Write exception?!?
>
> Taking a look at a snoop on the server, what I do notice is that after 
> accepting the socket from the agent, the server sends a FIN and then 
> immediately afterwards a RST. Normally there is an ACK in between, but in 
> this case the FIN doesn't even appear to wait before calling RST. What 
> causes this sort of sequence on the server socket?
>
> Could it be the backlog or some dynamic SYN ATTACK detection code that MS 
> has slipped into 2003 Server? Any ideas appreciated. And remember this is 
> intermittent and it only seems to happen with Windows Servers. NOTE: If I 
> use Linux or Solaris as a server we do not get this intermittent issue.
>
> FWIW, this is Java and RMI; however, I don't think that is part of the 
> issue. TIA.
>
> (Also, if there is a better forum to post this, let me know)
>
> R.
>

date: Sat, 19 Nov 2005 09:19:38 +0200   author:   Arkady Frenkel