jakarta-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Milamber <milam...@apache.org>
Subject Re: Lots of CLOSE_WAIT with HC4 HTTP implementation
Date Wed, 21 Sep 2011 23:44:23 GMT


Le 21/09/2011 23:13, Milamber a ecrit :
>
> Le 21/09/2011 22:42, sebb a ecrit :
>   
>> On 21 September 2011 22:29, Milamber <milamber@apache.org> wrote:
>>   
>>     
>>> [snip]
>>>
>>> I make a tcp dump and analyze with wireshark.
>>> With HC3.1 : 0-42 secs : 43 TCP conversations (inside several HTTP GET
>>> and response)
>>> With HC4.1 : 0-44 secs : 3011 TCP conversations (inside one HTTP GET and
>>> one response)
>>>     
>>>       
>> Do you mean that each HC4.1 conversation only contains a single
>> request/response?
>>   
>>     
> Yes a single request/response
>   
Mistake : HC4 conversation (follow tcp stream) show multiple GET / for
the same ressource (always same)

More precisions with the new test case (1 thread/39 request/30sec duration)

===
Tcp dump With HC4 (39 conn esta):
60 conversations.

Each conversations show multiple GET /imagexxx.png (always the same
resource per conversation)

===

Tcp dump with HC3 (1 conn esta):
1 tcp conversations

All requests in one keep alive connection (it's a CDN server)

===

>   
>> Can you enable debug logging for HTTPHC4Impl ?
>>   
>>     
> Yes I can, I will sent the log in a private mail
> see end of log : one user but lot of:
> 2011/09/22 01:06:56 DEBUG - jmeter.protocol.http.sampler.HTTPHC4Impl:
> Thread Finished
> 2011/09/22 01:06:56 DEBUG - jmeter.protocol.http.sampler.HTTPHC4Impl:
> Thread Finished
>
>
>   
>> This should show if the clients are being reused or not.
>>
>> I suggest you reduce thread and loop counts, or the log file will be very big.
>>   
>>     
> Done: 1 thread, 1 sec ramp up, 30 secs duration
>
> Starting the test @ Thu Sep 22 01:06:25 CEST 2011 (1316646385910)
> Waiting for possible shutdown message on port 4445
> summary +   188 in   3,7s =   50,9/s Avg:    18 Min:     8 Max:   113
> Err:     0 (0,00%)
> summary +  1697 in  26,1s =   65,1/s Avg:    14 Min:     8 Max:   173
> Err:     0 (0,00%)
> summary =  1885 in  29,8s =   63,3/s Avg:    15 Min:     8 Max:   173
> Err:     0 (0,00%)
> Tidying up ...    @ Thu Sep 22 01:06:56 CEST 2011 (1316646416091)
> ... end of run
>
>
>
> netstat -tplna| grep java | grep ESTA | wc -l
> 39 (esta conn)
>
> ==> 39 is the number of http requests in my test plan
>
>
>   
>> [I think we need to fix this before releasing 2.5.1]
>>   
>>     
>
> Yes sure.
>
>
>   
>>   
>>     
>>> HTTP conversations show Keep-Alive header (HC3 and HC4)
>>>
>>> I suppose that is a close keep alive connection problem with JMeter.
>>> Perhaps 2 issues are linked?
>>>     
>>>       
>> Dunno yet.
>>
>>   
>>     
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org


Mime
View raw message