Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
Hello, (on JMeter 2.5.1RC1) Don't retry automatically with HC4 sampler seems introduce a bug on load tests using HC4. When you run a load test, some errors The target server failed to respond can appear on response data. With wireshark, this error arrives at the end of TCP conversations: the GET request is sent, but no server response (the connection has been closed, I suppose). If I changes the property httpclient4.retrycount to 3, the load tests works fine, with no errors. This bug is tested on Linux with JVM5/7 and WinXP with JVM7 Test case is the Simple Test Case on this bugs: https://issues.apache.org/bugzilla/show_bug.cgi?id=51863 (Note: no errors with HC3.1) (Questions: retrycount exists on HC3.1? if yes what default value?) Response data org.apache.http.NoHttpResponseException: The target server failed to respond at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:101) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252) at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281) at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247) at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:265) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1010) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:996) at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:383) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:276) at java.lang.Thread.run(Thread.java:595) = Milamber Le 01/09/2011 17:52, s...@apache.org a ecrit : Author: sebb Date: Thu Sep 1 17:52:41 2011 New Revision: 1164186 URL: http://svn.apache.org/viewvc?rev=1164186view=rev Log: Don't automatically retry with HttpCLient4 sampler Modified: jakarta/jmeter/trunk/bin/jmeter.properties jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java jakarta/jmeter/trunk/xdocs/changes.xml jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml Modified: jakarta/jmeter/trunk/bin/jmeter.properties URL: http://svn.apache.org/viewvc/jakarta/jmeter/trunk/bin/jmeter.properties?rev=1164186r1=1164185r2=1164186view=diff == --- jakarta/jmeter/trunk/bin/jmeter.properties (original) +++ jakarta/jmeter/trunk/bin/jmeter.properties Thu Sep 1 17:52:41 2011 @@ -251,7 +251,7 @@ log_level.jorphan=INFO # 0 now means don't retry connection (in 2.3 and before it meant no tries at all!) #--- -# HTTPClient configuration +# Commons HTTPClient configuration #--- # define a properties file for overriding Commons HttpClient parameters @@ -302,7 +302,7 @@ log_level.jorphan=INFO #log_file.httpclient=httpclient.log -# Apache HttpClient logging examples +# Apache Commons HttpClient logging examples # # Enable header wire + context logging - Best for Debugging #log_level.org.apache.http=DEBUG @@ -320,6 +320,13 @@ log_level.jorphan=INFO #log_level.org.apache.http.client=DEBUG #--- +# Apache HttpComponents HTTPClient configuration (HTTPClient4) +#--- + +# Number of retries to attempt (default 0) +#httpclient4.retrycount=0 + +#--- # Results file configuration #--- Modified: jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java URL:
Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
Hello, Don't you think you should keep default to 0 and add same configuration to HTTPHC3 ? Maybe it's a real server issue that is hidden by retry set to 3. Can't we check in Jakarta apache logs to see if these errors are mentionned ? Regards Philippe On Fri, Sep 23, 2011 at 11:12 AM, Milamber milam...@apache.org wrote: Hello, (on JMeter 2.5.1RC1) Don't retry automatically with HC4 sampler seems introduce a bug on load tests using HC4. When you run a load test, some errors The target server failed to respond can appear on response data. With wireshark, this error arrives at the end of TCP conversations: the GET request is sent, but no server response (the connection has been closed, I suppose). If I changes the property httpclient4.retrycount to 3, the load tests works fine, with no errors. This bug is tested on Linux with JVM5/7 and WinXP with JVM7 Test case is the Simple Test Case on this bugs: https://issues.apache.org/bugzilla/show_bug.cgi?id=51863 (Note: no errors with HC3.1) (Questions: retrycount exists on HC3.1? if yes what default value?) Response data org.apache.http.NoHttpResponseException: The target server failed to respond at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:101) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252) at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281) at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247) at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:265) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1010) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:996) at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:383) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:276) at java.lang.Thread.run(Thread.java:595) = Milamber Le 01/09/2011 17:52, s...@apache.org a ecrit : Author: sebb Date: Thu Sep 1 17:52:41 2011 New Revision: 1164186 URL: http://svn.apache.org/viewvc?rev=1164186view=rev Log: Don't automatically retry with HttpCLient4 sampler Modified: jakarta/jmeter/trunk/bin/jmeter.properties jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java jakarta/jmeter/trunk/xdocs/changes.xml jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml Modified: jakarta/jmeter/trunk/bin/jmeter.properties URL: http://svn.apache.org/viewvc/jakarta/jmeter/trunk/bin/jmeter.properties?rev=1164186r1=1164185r2=1164186view=diff == --- jakarta/jmeter/trunk/bin/jmeter.properties (original) +++ jakarta/jmeter/trunk/bin/jmeter.properties Thu Sep 1 17:52:41 2011 @@ -251,7 +251,7 @@ log_level.jorphan=INFO # 0 now means don't retry connection (in 2.3 and before it meant no tries at all!) #--- -# HTTPClient configuration +# Commons HTTPClient configuration #--- # define a properties file for overriding Commons HttpClient parameters @@ -302,7 +302,7 @@ log_level.jorphan=INFO #log_file.httpclient=httpclient.log -# Apache HttpClient logging examples +# Apache Commons HttpClient logging examples # # Enable header wire + context logging - Best for Debugging #log_level.org.apache.http=DEBUG @@ -320,6 +320,13 @@ log_level.jorphan=INFO #log_level.org.apache.http.client=DEBUG #--- +# Apache HttpComponents HTTPClient configuration (HTTPClient4) +#--- + +# Number of retries to attempt (default 0) +#httpclient4.retrycount=0 +
Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
Again, I just implemented Retry on HTTPHC3.1 setting it to 0 and I get low 0.12% error like with HTTP 4.1. Do you want me to submit a patch to HTTPHC3.1 ? Regards Philippe On Fri, Sep 23, 2011 at 2:23 PM, Philippe Mouawad philippe.moua...@gmail.com wrote: Hello, Don't you think you should keep default to 0 and add same configuration to HTTPHC3 ? Maybe it's a real server issue that is hidden by retry set to 3. Can't we check in Jakarta apache logs to see if these errors are mentionned ? Regards Philippe On Fri, Sep 23, 2011 at 11:12 AM, Milamber milam...@apache.org wrote: Hello, (on JMeter 2.5.1RC1) Don't retry automatically with HC4 sampler seems introduce a bug on load tests using HC4. When you run a load test, some errors The target server failed to respond can appear on response data. With wireshark, this error arrives at the end of TCP conversations: the GET request is sent, but no server response (the connection has been closed, I suppose). If I changes the property httpclient4.retrycount to 3, the load tests works fine, with no errors. This bug is tested on Linux with JVM5/7 and WinXP with JVM7 Test case is the Simple Test Case on this bugs: https://issues.apache.org/bugzilla/show_bug.cgi?id=51863 (Note: no errors with HC3.1) (Questions: retrycount exists on HC3.1? if yes what default value?) Response data org.apache.http.NoHttpResponseException: The target server failed to respond at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:101) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252) at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281) at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247) at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:265) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1010) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:996) at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:383) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:276) at java.lang.Thread.run(Thread.java:595) = Milamber Le 01/09/2011 17:52, s...@apache.org a ecrit : Author: sebb Date: Thu Sep 1 17:52:41 2011 New Revision: 1164186 URL: http://svn.apache.org/viewvc?rev=1164186view=rev Log: Don't automatically retry with HttpCLient4 sampler Modified: jakarta/jmeter/trunk/bin/jmeter.properties jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java jakarta/jmeter/trunk/xdocs/changes.xml jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml Modified: jakarta/jmeter/trunk/bin/jmeter.properties URL: http://svn.apache.org/viewvc/jakarta/jmeter/trunk/bin/jmeter.properties?rev=1164186r1=1164185r2=1164186view=diff == --- jakarta/jmeter/trunk/bin/jmeter.properties (original) +++ jakarta/jmeter/trunk/bin/jmeter.properties Thu Sep 1 17:52:41 2011 @@ -251,7 +251,7 @@ log_level.jorphan=INFO # 0 now means don't retry connection (in 2.3 and before it meant no tries at all!) #--- -# HTTPClient configuration +# Commons HTTPClient configuration #--- # define a properties file for overriding Commons HttpClient parameters @@ -302,7 +302,7 @@ log_level.jorphan=INFO #log_file.httpclient=httpclient.log -# Apache HttpClient logging examples +# Apache Commons HttpClient logging examples # # Enable header wire + context logging - Best for Debugging #log_level.org.apache.http=DEBUG @@ -320,6 +320,13 @@ log_level.jorphan=INFO #log_level.org.apache.http.client=DEBUG
Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
Done: https://issues.apache.org/bugzilla/attachment.cgi?bugid=51882 Regards Philippe On Fri, Sep 23, 2011 at 2:34 PM, sebb seb...@gmail.com wrote: On 23 September 2011 13:29, Philippe Mouawad philippe.moua...@gmail.com wrote: Again, I just implemented Retry on HTTPHC3.1 setting it to 0 and I get low 0.12% error like with HTTP 4.1. Do you want me to submit a patch to HTTPHC3.1 ? Would be useful, thanks. Regards Philippe On Fri, Sep 23, 2011 at 2:23 PM, Philippe Mouawad philippe.moua...@gmail.com wrote: Hello, Don't you think you should keep default to 0 and add same configuration to HTTPHC3 ? Maybe it's a real server issue that is hidden by retry set to 3. Can't we check in Jakarta apache logs to see if these errors are mentionned ? Regards Philippe On Fri, Sep 23, 2011 at 11:12 AM, Milamber milam...@apache.org wrote: Hello, (on JMeter 2.5.1RC1) Don't retry automatically with HC4 sampler seems introduce a bug on load tests using HC4. When you run a load test, some errors The target server failed to respond can appear on response data. With wireshark, this error arrives at the end of TCP conversations: the GET request is sent, but no server response (the connection has been closed, I suppose). If I changes the property httpclient4.retrycount to 3, the load tests works fine, with no errors. This bug is tested on Linux with JVM5/7 and WinXP with JVM7 Test case is the Simple Test Case on this bugs: https://issues.apache.org/bugzilla/show_bug.cgi?id=51863 (Note: no errors with HC3.1) (Questions: retrycount exists on HC3.1? if yes what default value?) Response data org.apache.http.NoHttpResponseException: The target server failed to respond at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:101) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252) at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281) at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247) at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:265) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1010) at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:996) at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:383) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:276) at java.lang.Thread.run(Thread.java:595) = Milamber Le 01/09/2011 17:52, s...@apache.org a ecrit : Author: sebb Date: Thu Sep 1 17:52:41 2011 New Revision: 1164186 URL: http://svn.apache.org/viewvc?rev=1164186view=rev Log: Don't automatically retry with HttpCLient4 sampler Modified: jakarta/jmeter/trunk/bin/jmeter.properties jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java jakarta/jmeter/trunk/xdocs/changes.xml jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml Modified: jakarta/jmeter/trunk/bin/jmeter.properties URL: http://svn.apache.org/viewvc/jakarta/jmeter/trunk/bin/jmeter.properties?rev=1164186r1=1164185r2=1164186view=diff == --- jakarta/jmeter/trunk/bin/jmeter.properties (original) +++ jakarta/jmeter/trunk/bin/jmeter.properties Thu Sep 1 17:52:41 2011 @@ -251,7 +251,7 @@ log_level.jorphan=INFO # 0 now means don't retry connection (in 2.3 and before it meant no tries at all!) #--- -# HTTPClient configuration +# Commons HTTPClient configuration #--- # define a properties file for overriding Commons HttpClient
Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
Le 23/09/2011 12:07, sebb a ecrit : On 23 September 2011 10:12, Milamber milam...@apache.org wrote: Hello, (on JMeter 2.5.1RC1) Don't retry automatically with HC4 sampler seems introduce a bug on load tests using HC4. When you run a load test, some errors The target server failed to respond can appear on response data. With wireshark, this error arrives at the end of TCP conversations: the GET request is sent, but no server response (the connection has been closed, I suppose). If I changes the property httpclient4.retrycount to 3, the load tests works fine, with no errors. This bug is tested on Linux with JVM5/7 and WinXP with JVM7 Test case is the Simple Test Case on this bugs: https://issues.apache.org/bugzilla/show_bug.cgi?id=51863 (Note: no errors with HC3.1) (Questions: retrycount exists on HC3.1? if yes what default value?) Looks like the HC3.1 retry count also defaults to 3. I don't now remember exactly why I overrode the setting. I vaguely remember seeing some retries in a test I was doing, and thinking it would be better to know about them. It is possible to revert to the previous behaviour - just define the JMeter property: httpclient4.retrycount=3 Could you retry the test with that setting and see if that fixes the bahaviour for you? Yes with retrycount=3 and HC4, no errors (see above). Milamber S. - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
Hello, I've relaunched some tests with a new SimpleTest.jmx version which generate an unique URL for each request (in attachment) I did a analysis with wireshark to find the retries GET (same unique url call 2 times) NB retries GET means: GET /unique_url at end of TCP conversations without response, and a new retry GET /unique_url at the begin of TCP conversations Results (with 2.5.1RC1): a) Java and HC3.1 (and HC4) have retries GET b) The load test make ~15745 requests. * With Java : 670 retries GET * With HC3.1 (retrycount default) : 536 retries GET * With HC4 (retrycount force to 3) : 571 retries GET I suppose that the retrycount default value to 3 (or 1) is needed for HC4. Milamber Le 23/09/2011 12:58, sebb a ecrit : Has anyone seen the errors with the Java implementation? There does not seem to be any documentation [1] on how many retries it does, but I have seen something that suggests it normally retries just once. [1] http://download.oracle.com/javase/6/docs/technotes/guides/net/properties.html - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org ?xml version=1.0 encoding=UTF-8? jmeterTestPlan version=1.2 properties=2.1 hashTree TestPlan guiclass=TestPlanGui testclass=TestPlan testname=Plan de test enabled=true stringProp name=TestPlan.comments/stringProp boolProp name=TestPlan.functional_modefalse/boolProp boolProp name=TestPlan.serialize_threadgroupsfalse/boolProp elementProp name=TestPlan.user_defined_variables elementType=Arguments guiclass=ArgumentsPanel testclass=Arguments testname=User Defined Variables enabled=true collectionProp name=Arguments.arguments/ /elementProp stringProp name=TestPlan.user_define_classpath/stringProp /TestPlan hashTree ConfigTestElement guiclass=HttpDefaultsGui testclass=ConfigTestElement testname=HTTP Request Defaults enabled=true elementProp name=HTTPsampler.Arguments elementType=Arguments guiclass=HTTPArgumentsPanel testclass=Arguments testname=Variables pré-définies enabled=true collectionProp name=Arguments.arguments/ /elementProp stringProp name=HTTPSampler.domainjakarta.apache.org/stringProp stringProp name=HTTPSampler.port/stringProp stringProp name=HTTPSampler.connect_timeout/stringProp stringProp name=HTTPSampler.response_timeout/stringProp stringProp name=HTTPSampler.protocol/stringProp stringProp name=HTTPSampler.contentEncoding/stringProp stringProp name=HTTPSampler.path/stringProp stringProp name=HTTPSampler.implementationHttpClient4/stringProp stringProp name=HTTPSampler.concurrentPool4/stringProp /ConfigTestElement hashTree/ CookieManager guiclass=CookiePanel testclass=CookieManager testname=Gestionnaire de cookies HTTP enabled=true collectionProp name=CookieManager.cookies/ boolProp name=CookieManager.clearEachIterationtrue/boolProp /CookieManager hashTree/ CounterConfig guiclass=CounterConfigGui testclass=CounterConfig testname=Counter enabled=true stringProp name=CounterConfig.start1/stringProp stringProp name=CounterConfig.end/stringProp stringProp name=CounterConfig.incr1/stringProp stringProp name=CounterConfig.nameCPT/stringProp stringProp name=CounterConfig.format00/stringProp boolProp name=CounterConfig.per_userfalse/boolProp /CounterConfig hashTree/ ThreadGroup guiclass=ThreadGroupGui testclass=ThreadGroup testname=Thread Group enabled=true stringProp name=ThreadGroup.on_sample_errorcontinue/stringProp elementProp name=ThreadGroup.main_controller elementType=LoopController guiclass=LoopControlPanel testclass=LoopController testname=Loop Controller enabled=true boolProp name=LoopController.continue_foreverfalse/boolProp intProp name=LoopController.loops-1/intProp /elementProp stringProp name=ThreadGroup.num_threads100/stringProp stringProp name=ThreadGroup.ramp_time100/stringProp longProp name=ThreadGroup.start_time1316642573000/longProp longProp name=ThreadGroup.end_time1316642573000/longProp boolProp name=ThreadGroup.schedulertrue/boolProp stringProp name=ThreadGroup.duration300/stringProp stringProp name=ThreadGroup.delay/stringProp /ThreadGroup hashTree HTTPSamplerProxy guiclass=HttpTestSampleGui testclass=HTTPSamplerProxy testname=1 HTTP Request enabled=true elementProp name=HTTPsampler.Arguments elementType=Arguments guiclass=HTTPArgumentsPanel testclass=Arguments testname=Variables pré-définies enabled=true collectionProp name=Arguments.arguments/ /elementProp stringProp name=HTTPSampler.domain/stringProp stringProp
Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
On 23 September 2011 15:20, Milamber milam...@apache.org wrote: Hello, I've relaunched some tests with a new SimpleTest.jmx version which generate an unique URL for each request (in attachment) I did a analysis with wireshark to find the retries GET (same unique url call 2 times) NB retries GET means: GET /unique_url at end of TCP conversations without response, and a new retry GET /unique_url at the begin of TCP conversations Results (with 2.5.1RC1): a) Java and HC3.1 (and HC4) have retries GET b) The load test make ~15745 requests. * With Java : 670 retries GET * With HC3.1 (retrycount default) : 536 retries GET * With HC4 (retrycount force to 3) : 571 retries GET Were any requests retried *more* than once in any of the implementations? It would be interesting to know if the Java implementation can retry more than once. I suppose that the retrycount default value to 3 (or 1) is needed for HC4. For backwards compatibility (and compatibility with HC3), then we should choose 3. I asked on the HC mailing list, and the choice of 3 was arbitrary. For compatibility with Java we should probably set them both to 1. I think 1 might be the best compromise - should catch most errors. In any case, we need to document the settings. I'll add some text to component reference shortly. Milamber Le 23/09/2011 12:58, sebb a ecrit : Has anyone seen the errors with the Java implementation? There does not seem to be any documentation [1] on how many retries it does, but I have seen something that suggests it normally retries just once. [1] http://download.oracle.com/javase/6/docs/technotes/guides/net/properties.html - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
Re: svn commit: r1164186 - in /jakarta/jmeter/trunk: bin/jmeter.properties src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java xdocs/changes.xml xdocs/usermanual/component_refer
Le 23/09/2011 14:34, sebb a ecrit : On 23 September 2011 15:20, Milamber milam...@apache.org wrote: Hello, I've relaunched some tests with a new SimpleTest.jmx version which generate an unique URL for each request (in attachment) I did a analysis with wireshark to find the retries GET (same unique url call 2 times) NB retries GET means: GET /unique_url at end of TCP conversations without response, and a new retry GET /unique_url at the begin of TCP conversations Results (with 2.5.1RC1): a) Java and HC3.1 (and HC4) have retries GET b) The load test make ~15745 requests. * With Java : 670 retries GET * With HC3.1 (retrycount default) : 536 retries GET * With HC4 (retrycount force to 3) : 571 retries GET Were any requests retried *more* than once in any of the implementations? It would be interesting to know if the Java implementation can retry more than once. 0 request retried more than once for JAVA / HC 3 / HC 4 I suppose that the retrycount default value to 3 (or 1) is needed for HC4. For backwards compatibility (and compatibility with HC3), then we should choose 3. I asked on the HC mailing list, and the choice of 3 was arbitrary. For compatibility with Java we should probably set them both to 1. I think 1 might be the best compromise - should catch most errors. 1 retry count seems the good value from RFC HTTP/1.1 Keep-alive : Clients which assume persistent connections and pipeline immediately after connection establishment SHOULD be prepared to retry their connection* if the first pipelined attempt fails*. If a client does such a retry, it MUST NOT pipeline before it knows the connection is persistent. Clients MUST also be prepared to resend their requests if the server closes the connection before sending all of the corresponding responses. http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1.2.2 Milamber In any case, we need to document the settings. I'll add some text to component reference shortly. Milamber Le 23/09/2011 12:58, sebb a ecrit : Has anyone seen the errors with the Java implementation? There does not seem to be any documentation [1] on how many retries it does, but I have seen something that suggests it normally retries just once. [1] http://download.oracle.com/javase/6/docs/technotes/guides/net/properties.html - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
