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=7&rev2=8 * httpclient4.retrycount=1 + This will make JMeter retry once. For !HttpClient 3, in user.properties set: - This will make JMeter retry once. - For !HttpClient 3, in user.properties set: * httpclient3.retrycount=1 @@ -59, +58 @@ * http.connection.stalecheck$Boolean=true ==== New setting in JMeter 2.12 ==== - Upcoming version of JMeter adds a setting to add an idle connection timeout if the server does not send Keep-Alive headers. This value is in milliseconds: @@ -67, +65 @@ * httpclient4.idletimeout=<time in ms> === Interesting links: === - * https://issues.apache.org/bugzilla/show_bug.cgi?id=56119 + * https://issues.apache.org/bugzilla/show_bug.cgi?id=56119 - * http://stackoverflow.com/questions/4798461/cneonction-and-nncoection-http-headers + * 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 + You may have this kind of issues even with retry and stale check enabled, in this case check server configuration and load. - server configuration and load. === Author: === - Philippe M. + [[http://twitter.com/philmdot|Philippe M.]]
