Re: TCP & curl-loader question
Status: Alpha
Brought to you by:
coroberti
From: Robert I. <cor...@gm...> - 2008-11-01 14:22:34
|
On Sat, Nov 1, 2008 at 2:47 AM, Gary Fitts <ga...@in...> wrote: > Hello Robert, > > I've run into a problem that seems unrelated to the curl-loader extensions > I'm building. This occurs whenever I have two or more virtual clients > running simultaneously. Here's what I see when I look at the TCP traffic > with Wireshark: > > Roughly half the clients proceed normally. The server sends the final > response of the conversation, the client ACKs this, and then the client > initiates a FIN-ACK and the server replies with FIN-ACK. That's it, and > everyone's happy. > > But with the rest of the clients, something happens in the middle of the > conversation, before the client is ready to finish. The server replies to a > client request, the client ACKs this reply, and then the server unexpectedly > initiates a FIN-ACK. The client responds with two RST packets, but the > server doesn't react, and the client times out. > Could it be, that your URL_COMPLETION_TIMEOUT value is too short and you need to increase it? It may happen, when POST-ing is accompanied by 100-Continue as seen in your log file. -- Truly, Robert Iakobashvili, Ph.D. ...................................................................... www.ghotit.com Assistive technology that understands you ...................................................................... |