jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jmeter Wiki] Update of "JMeterSocketClosed" by Philippe Mouawad
Date Tue, 01 Apr 2014 19:37:06 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jmeter Wiki" for change notification.

The "JMeterSocketClosed" page has been changed by Philippe Mouawad:
https://wiki.apache.org/jmeter/JMeterSocketClosed?action=diff&rev1=4&rev2=5

Comment:
Fix some typos

   * Socket closed
   * Non HTTP response code: org.apache.http.NoHttpResponseException (the target server failed
to respond)
  
- Note that article is about increase in this type of errors.
- 
  === Explanation ===
  The increase of this type of errors can be explained by two settings changes:
  
-  * retry of failing request (idempotent) has been disabled in JMeter 2.10
+  * retry of failing request (idempotent ones only) has been disabled in JMeter 2.10
   * stale check in HTTP Client 3 and 4 implementations has been disabled in JMeter 2.11
  
  === Why these changes? ===
- Previous retry default settings led to increased number of Requests in certain type of failures
Previous stale check was a bit expensive, as it applied to every sample.
+ Previous retry default settings led to increased number of Requests in certain type of failures.
  
- That is why the default was changed to disable it.
+ Previous stale check was a bit expensive, as it applied to every sample. That is why the
default was changed to disable it.
  
  Retry or stale check can hide issues on Server configuration:
  
   * Server failing to handle correctly Keep-Alive header
-  * Overwhelmed server refusing connection, retrying can increase load
+  * Overwhelmed server refusing connection, retrying would increase load
  
  === Changing configuration: ===
- If you think this server behaviour is OK, then configuration can be changed in two places:
+ If you think this server behavior is OK, then configuration can be changed in two places:
  
  ==== Enabling retry ====
  For HttpClient 4, in user.properties set :
  
-  * httpclient4.retrycount=0
+  * httpclient4.retrycount=1
  
+ This will make JMeter retry once.
  For HttpClient 3, in user.properties set:
  
-  * httpclient3.retrycount=0
+  * httpclient3.retrycount=1
+ 
+ This will make JMeter retry once.
  
  ==== Enabling stale check ====
  For HC4 Implementation:
@@ -58, +59 @@

   * http.connection.stalecheck$Boolean=true
  
  ==== New setting in JMeter 2.12 ====
+ 
- Upcoming version of JMeter will add a setting to add connection timeout  if the server does
not send Keep-Alive headers.
+ Upcoming version of JMeter adds a setting to add connection timeout if the server does not
send Keep-Alive headers.
  
  This value is in milliseconds:
  
-  * httpclient4.idletimeout=<>
+  * httpclient4.idletimeout=<time in ms>
  
  === Interesting links: ===
   *  https://issues.apache.org/bugzilla/show_bug.cgi?id=56119
  
   *  http://stackoverflow.com/questions/4798461/cneonction-and-nncoection-http-headers
  
+ === Scope of document ===
+ This article is about the increase of Socket closed error.
+ 
+ You may have this kind of issues even with retry and stale check enabled, in this case check
+ server configuration and load.
+ 
  === Author: ===
  Philippe M.
  

Mime
View raw message