jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 60492] HttpClient4 implementation couldn't reuse client socket when using KeepAlive
Date Sat, 24 Dec 2016 05:23:17 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=60492

Liu XP <liu_xp2003@sina.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #5 from Liu XP <liu_xp2003@sina.com> ---
My web server used tomcat 8 with default setting. 
I paid attention to this behaviour duration backend web micro service stress
testing.
I not sure whether it is right for my testing using HttpClient 4, but the
behaviour is different with HttpClient 3.1.

Thank you for your suggestion. I verified using different value of
"httpclient4.time_to_live" again.
When I using default value and testing sina web site with one thread, I could
see new socket created in a short time. And previous socket was changed to
TIME_WAIT.
C:\windows\system32>netstat -na|grep 105:80
  TCP    192.168.1.111:36577    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36578    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36581    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36583    140.211.11.105:80      FIN_WAIT_1
  TCP    192.168.1.111:36587    140.211.11.105:80      ESTABLISHED

After I changed httpclient4.time_to_live value to 10,000, I restarted JMeter
and ran same test script again. I could see new socket created not frequently.
C:\windows\system32>netstat -na|grep 105:80
  TCP    192.168.1.111:36654    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36657    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36661    140.211.11.105:80      ESTABLISHED

C:\windows\system32>netstat -na|grep 105:80
  TCP    192.168.1.111:36654    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36657    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36661    140.211.11.105:80      TIME_WAIT
  TCP    192.168.1.111:36664    140.211.11.105:80      SYN_SENT

To simulate end user behaviour, I believe the default setting is reasonable.
Do you have suggestion about value of httpclient4.time_to_live parameter, when
running simulate testing between two server with KeepAlive?

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message