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: [VOTE] Release JMeter 2.5.1 RC1
Hello, I reproduce your issue (not sure it's a new one). I opened https://issues.apache.org/bugzilla/show_bug.cgi?id=51880 and submitted a patch. Can you test to tell if it's OK for you ? Regards Philippe Mouawad 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com One update: The shutdown command is not working if I invoke it before all the thread are started. eg. If I start 20 thread and call it before the 20 are started, it fails. If I call it once the 20 thread are started, it works. The 'Stop' command works in both cases. Regards, Stef 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com Hi, If I try to stop a running test using Shutdown, it never stops (even if thread count is reduced till 0) and the windows stays open. I have to close it and call stop to have the top left green box back to gray. Can someone confirm this? JMeter 2.5.1 r1174406, win xp sp3 32bits, jdk 1.6. Regards, Stef On Fri, Sep 23, 2011 at 4:37 AM, Peter Lin wool...@gmail.com wrote: +1 On Thu, Sep 22, 2011 at 6:53 PM, Milamber milam...@apache.org wrote: Hello, The first release candidate for JMeter 2.5.1 has been prepared, and your votes are solicited. This release fixes mainly some bugs appeared since JMeter 2.5, but contains few improvements. Tests (load tests or functional tests) with JVM 5/6/7 on Linux/Windows/Mac OS on functionality changes are welcomes (HttpClient 4.1 request, Http request with parallels embedded resources, View results tree, WebServices (SOAP) request, etc) List of changes: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version is targeted at Java 1.5+. Archives/hashes/sigs and RAT report: http://people.apache.org/~milamber/jmeter-2.5.1RC1/dist MD5 hashes of archives for this vote: c1c63f36692ac2fd2e7cca2f2b162c6e *jakarta-jmeter-2.5.1.tgz 8345f36f769872651d53db2436eac100 *jakarta-jmeter-2.5.1.zip c232ea7259543592f56c2dca7ba5850d *jakarta-jmeter-2.5.1_src.tgz 52a2dee578fd433d286e16dfe928b6b2 *jakarta-jmeter-2.5.1_src.zip Site Docs are here: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_1_RC1(r1174408) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://people.apache.org/~milamber/ N.B. To download the dependencies: ant download_jars To create the jars and test JMeter: ant package test. JMeter 2.5 requires Java 1.5 or later. Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber - 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 -- Cordialement. Philippe Mouawad. Ubik-Ingénierie
Re: [VOTE] Release JMeter 2.5.1 RC1
On 23 September 2011 11:29, sebb seb...@gmail.com wrote: 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com: One update: The shutdown command is not working if I invoke it before all the thread are started. eg. If I start 20 thread and call it before the 20 are started, it fails. If I call it once the 20 thread are started, it works. The 'Stop' command works in both cases. The Shutdown command just sets a flag to tell the threads to stop; the Stop command actually interrupts the threads. Probably the flag is not being checked at startup. Yes, that is the case. Shutdown does actually work, but it currently waits for the Ramp-Up delay to complete. Obviously this is not ideal; will fix it shortly. Regards, Stef 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com Hi, If I try to stop a running test using Shutdown, it never stops (even if thread count is reduced till 0) and the windows stays open. I have to close it and call stop to have the top left green box back to gray. Can someone confirm this? JMeter 2.5.1 r1174406, win xp sp3 32bits, jdk 1.6. Regards, Stef On Fri, Sep 23, 2011 at 4:37 AM, Peter Lin wool...@gmail.com wrote: +1 On Thu, Sep 22, 2011 at 6:53 PM, Milamber milam...@apache.org wrote: Hello, The first release candidate for JMeter 2.5.1 has been prepared, and your votes are solicited. This release fixes mainly some bugs appeared since JMeter 2.5, but contains few improvements. Tests (load tests or functional tests) with JVM 5/6/7 on Linux/Windows/Mac OS on functionality changes are welcomes (HttpClient 4.1 request, Http request with parallels embedded resources, View results tree, WebServices (SOAP) request, etc) List of changes: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version is targeted at Java 1.5+. Archives/hashes/sigs and RAT report: http://people.apache.org/~milamber/jmeter-2.5.1RC1/dist MD5 hashes of archives for this vote: c1c63f36692ac2fd2e7cca2f2b162c6e *jakarta-jmeter-2.5.1.tgz 8345f36f769872651d53db2436eac100 *jakarta-jmeter-2.5.1.zip c232ea7259543592f56c2dca7ba5850d *jakarta-jmeter-2.5.1_src.tgz 52a2dee578fd433d286e16dfe928b6b2 *jakarta-jmeter-2.5.1_src.zip Site Docs are here: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_1_RC1(r1174408) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://people.apache.org/~milamber/ N.B. To download the dependencies: ant download_jars To create the jars and test JMeter: ant package test. JMeter 2.5 requires Java 1.5 or later. Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber - 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 - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Thanks for the quick response! Yes it is a new issue, it was working fine in 2.5. Stef On Fri, Sep 23, 2011 at 3:48 PM, Philippe Mouawad philippe.moua...@gmail.com wrote: Hello, I reproduce your issue (not sure it's a new one). I opened https://issues.apache.org/bugzilla/show_bug.cgi?id=51880 and submitted a patch. Can you test to tell if it's OK for you ? Regards Philippe Mouawad 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com One update: The shutdown command is not working if I invoke it before all the thread are started. eg. If I start 20 thread and call it before the 20 are started, it fails. If I call it once the 20 thread are started, it works. The 'Stop' command works in both cases. Regards, Stef 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com Hi, If I try to stop a running test using Shutdown, it never stops (even if thread count is reduced till 0) and the windows stays open. I have to close it and call stop to have the top left green box back to gray. Can someone confirm this? JMeter 2.5.1 r1174406, win xp sp3 32bits, jdk 1.6. Regards, Stef On Fri, Sep 23, 2011 at 4:37 AM, Peter Lin wool...@gmail.com wrote: +1 On Thu, Sep 22, 2011 at 6:53 PM, Milamber milam...@apache.org wrote: Hello, The first release candidate for JMeter 2.5.1 has been prepared, and your votes are solicited. This release fixes mainly some bugs appeared since JMeter 2.5, but contains few improvements. Tests (load tests or functional tests) with JVM 5/6/7 on Linux/Windows/Mac OS on functionality changes are welcomes (HttpClient 4.1 request, Http request with parallels embedded resources, View results tree, WebServices (SOAP) request, etc) List of changes: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version is targeted at Java 1.5+. Archives/hashes/sigs and RAT report: http://people.apache.org/~milamber/jmeter-2.5.1RC1/dist MD5 hashes of archives for this vote: c1c63f36692ac2fd2e7cca2f2b162c6e *jakarta-jmeter-2.5.1.tgz 8345f36f769872651d53db2436eac100 *jakarta-jmeter-2.5.1.zip c232ea7259543592f56c2dca7ba5850d *jakarta-jmeter-2.5.1_src.tgz 52a2dee578fd433d286e16dfe928b6b2 *jakarta-jmeter-2.5.1_src.zip Site Docs are here: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_1_RC1(r1174408) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://people.apache.org/~milamber/ N.B. To download the dependencies: ant download_jars To create the jars and test JMeter: ant package test. JMeter 2.5 requires Java 1.5 or later. Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber - 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 -- Cordialement. Philippe Mouawad. Ubik-Ingénierie
Re: Classloading issue
On 20 September 2011 23:04, Philippe Mouawad philippe.moua...@gmail.com wrote:
Hello,
I am implementing a specific RequestView for a particular kind of requests.
I package my JAR and put it in lib/ext.
I run JMeter but my RequestView is not found.
I debugged RequestPanel constructor:
try {
classesToAdd =
JMeterUtils.findClassesThatExtend(RequestView.class);
} catch (IOException e1) {
// ignored
}
This finds my class.
But this code:
final RequestView requestView =
(RequestView) Class.forName(clazz).newInstance();
Fails with ClassNotFoundException.
To workaround I changed this to :
final RequestView requestView = (RequestView)
Thread.currentThread().getContextClassLoader().loadClass(clazz).newInstance();
and it worked.
Is there something wrong in my approach or should I submit a patch ?
This issue also occurs on 2.5
Just for completeness - this has been fixed, it was an issue with
Eclipse configuration, not JMeter.
I opened issue 51854.
Thank you
Regards
Philippe Mouawad
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
-
To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org
For additional commands, e-mail: dev-h...@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com: Thanks for the quick response! Yes it is a new issue, it was working fine in 2.5. Thanks for reviewing and reporting it. It was a side effect of the fix for Bug 51839 - ... end of run printed prematurely Now fixed in SVN. Stef On Fri, Sep 23, 2011 at 3:48 PM, Philippe Mouawad philippe.moua...@gmail.com wrote: Hello, I reproduce your issue (not sure it's a new one). I opened https://issues.apache.org/bugzilla/show_bug.cgi?id=51880 and submitted a patch. Can you test to tell if it's OK for you ? Regards Philippe Mouawad 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com One update: The shutdown command is not working if I invoke it before all the thread are started. eg. If I start 20 thread and call it before the 20 are started, it fails. If I call it once the 20 thread are started, it works. The 'Stop' command works in both cases. Regards, Stef 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com Hi, If I try to stop a running test using Shutdown, it never stops (even if thread count is reduced till 0) and the windows stays open. I have to close it and call stop to have the top left green box back to gray. Can someone confirm this? JMeter 2.5.1 r1174406, win xp sp3 32bits, jdk 1.6. Regards, Stef On Fri, Sep 23, 2011 at 4:37 AM, Peter Lin wool...@gmail.com wrote: +1 On Thu, Sep 22, 2011 at 6:53 PM, Milamber milam...@apache.org wrote: Hello, The first release candidate for JMeter 2.5.1 has been prepared, and your votes are solicited. This release fixes mainly some bugs appeared since JMeter 2.5, but contains few improvements. Tests (load tests or functional tests) with JVM 5/6/7 on Linux/Windows/Mac OS on functionality changes are welcomes (HttpClient 4.1 request, Http request with parallels embedded resources, View results tree, WebServices (SOAP) request, etc) List of changes: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version is targeted at Java 1.5+. Archives/hashes/sigs and RAT report: http://people.apache.org/~milamber/jmeter-2.5.1RC1/dist MD5 hashes of archives for this vote: c1c63f36692ac2fd2e7cca2f2b162c6e *jakarta-jmeter-2.5.1.tgz 8345f36f769872651d53db2436eac100 *jakarta-jmeter-2.5.1.zip c232ea7259543592f56c2dca7ba5850d *jakarta-jmeter-2.5.1_src.tgz 52a2dee578fd433d286e16dfe928b6b2 *jakarta-jmeter-2.5.1_src.zip Site Docs are here: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_1_RC1(r1174408) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://people.apache.org/~milamber/ N.B. To download the dependencies: ant download_jars To create the jars and test JMeter: ant package test. JMeter 2.5 requires Java 1.5 or later. Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber - 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 -- Cordialement. Philippe Mouawad. Ubik-Ingénierie - 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, 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: [VOTE] Release JMeter 2.5.1 RC1
Great! Thanks! Stef On Fri, Sep 23, 2011 at 5:24 PM, sebb seb...@gmail.com wrote: 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com: Thanks for the quick response! Yes it is a new issue, it was working fine in 2.5. Thanks for reviewing and reporting it. It was a side effect of the fix for Bug 51839 - ... end of run printed prematurely Now fixed in SVN. Stef On Fri, Sep 23, 2011 at 3:48 PM, Philippe Mouawad philippe.moua...@gmail.com wrote: Hello, I reproduce your issue (not sure it's a new one). I opened https://issues.apache.org/bugzilla/show_bug.cgi?id=51880 and submitted a patch. Can you test to tell if it's OK for you ? Regards Philippe Mouawad 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com One update: The shutdown command is not working if I invoke it before all the thread are started. eg. If I start 20 thread and call it before the 20 are started, it fails. If I call it once the 20 thread are started, it works. The 'Stop' command works in both cases. Regards, Stef 2011/9/23 Stéphane Hoblingre stephane.hoblin...@gmail.com Hi, If I try to stop a running test using Shutdown, it never stops (even if thread count is reduced till 0) and the windows stays open. I have to close it and call stop to have the top left green box back to gray. Can someone confirm this? JMeter 2.5.1 r1174406, win xp sp3 32bits, jdk 1.6. Regards, Stef On Fri, Sep 23, 2011 at 4:37 AM, Peter Lin wool...@gmail.com wrote: +1 On Thu, Sep 22, 2011 at 6:53 PM, Milamber milam...@apache.org wrote: Hello, The first release candidate for JMeter 2.5.1 has been prepared, and your votes are solicited. This release fixes mainly some bugs appeared since JMeter 2.5, but contains few improvements. Tests (load tests or functional tests) with JVM 5/6/7 on Linux/Windows/Mac OS on functionality changes are welcomes (HttpClient 4.1 request, Http request with parallels embedded resources, View results tree, WebServices (SOAP) request, etc) List of changes: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version is targeted at Java 1.5+. Archives/hashes/sigs and RAT report: http://people.apache.org/~milamber/jmeter-2.5.1RC1/dist MD5 hashes of archives for this vote: c1c63f36692ac2fd2e7cca2f2b162c6e *jakarta-jmeter-2.5.1.tgz 8345f36f769872651d53db2436eac100 *jakarta-jmeter-2.5.1.zip c232ea7259543592f56c2dca7ba5850d *jakarta-jmeter-2.5.1_src.tgz 52a2dee578fd433d286e16dfe928b6b2 *jakarta-jmeter-2.5.1_src.zip Site Docs are here: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_1_RC1(r1174408) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://people.apache.org/~milamber/ N.B. To download the dependencies: ant download_jars To create the jars and test JMeter: ant package test. JMeter 2.5 requires Java 1.5 or later. Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber - 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 -- Cordialement. Philippe Mouawad. Ubik-Ingénierie - 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
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: Classloading issue
Hello,
I added a note to:
- https://issues.apache.org/bugzilla/show_bug.cgi?id=51854
Regards
Philippe
On Fri, Sep 23, 2011 at 1:46 PM, sebb seb...@gmail.com wrote:
On 20 September 2011 23:04, Philippe Mouawad philippe.moua...@gmail.com
wrote:
Hello,
I am implementing a specific RequestView for a particular kind of
requests.
I package my JAR and put it in lib/ext.
I run JMeter but my RequestView is not found.
I debugged RequestPanel constructor:
try {
classesToAdd =
JMeterUtils.findClassesThatExtend(RequestView.class);
} catch (IOException e1) {
// ignored
}
This finds my class.
But this code:
final RequestView requestView =
(RequestView) Class.forName(clazz).newInstance();
Fails with ClassNotFoundException.
To workaround I changed this to :
final RequestView requestView = (RequestView)
Thread.currentThread().getContextClassLoader().loadClass(clazz).newInstance();
and it worked.
Is there something wrong in my approach or should I submit a patch ?
This issue also occurs on 2.5
Just for completeness - this has been fixed, it was an issue with
Eclipse configuration, not JMeter.
I opened issue 51854.
Thank you
Regards
Philippe Mouawad
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
-
To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org
For additional commands, e-mail: dev-h...@jakarta.apache.org
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
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
Re: [VOTE] Release JMeter 2.5.1 RC1
Hello, It's seems all open bugs with 2.5.1RC1 are closed. I will start the RC2 process tomorrow. Milamber Le 22/09/2011 22:53, Milamber a ecrit : Hello, The first release candidate for JMeter 2.5.1 has been prepared, and your votes are solicited. This release fixes mainly some bugs appeared since JMeter 2.5, but contains few improvements. Tests (load tests or functional tests) with JVM 5/6/7 on Linux/Windows/Mac OS on functionality changes are welcomes (HttpClient 4.1 request, Http request with parallels embedded resources, View results tree, WebServices (SOAP) request, etc) List of changes: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version is targeted at Java 1.5+. Archives/hashes/sigs and RAT report: http://people.apache.org/~milamber/jmeter-2.5.1RC1/dist MD5 hashes of archives for this vote: c1c63f36692ac2fd2e7cca2f2b162c6e *jakarta-jmeter-2.5.1.tgz 8345f36f769872651d53db2436eac100 *jakarta-jmeter-2.5.1.zip c232ea7259543592f56c2dca7ba5850d *jakarta-jmeter-2.5.1_src.tgz 52a2dee578fd433d286e16dfe928b6b2 *jakarta-jmeter-2.5.1_src.zip Site Docs are here: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_1_RC1 (r1174408) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://people.apache.org/~milamber/ N.B. To download the dependencies: ant download_jars To create the jars and test JMeter: ant package test. JMeter 2.5 requires Java 1.5 or later. Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber - 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
Nightly builds
Hello, I have a question regarding nightly builds, when are they built ? Why for example do we have one with date 09/21 while there has been patches yesterday and today ? Is there some delay ? Thanks Regards Philippe Mouawad
Re: request to be added to the contributors list
On 23 September 2011 20:49, Franco Sabadini fsab...@gmail.com wrote: Hi, I helped on resolving *Bug 30563*https://issues.apache.org/bugzilla/show_bug.cgi?id=30563and I wanted to add myself to the contributors list on http://wiki.apache.org/jakarta-jmeter/JMeterCommitters but I can't seem to be able to edit it, can u add me or give me the needed permissions? My wiki username is FrancoSabadini. Try now. Thanks. Franco - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
Re: request to be added to the contributors list
worked great :-). Thanks. Franco On Fri, Sep 23, 2011 at 3:39 PM, sebb seb...@gmail.com wrote: On 23 September 2011 20:49, Franco Sabadini fsab...@gmail.com wrote: Hi, I helped on resolving *Bug 30563*https://issues.apache.org/bugzilla/show_bug.cgi?id=30563and I wanted to add myself to the contributors list on http://wiki.apache.org/jakarta-jmeter/JMeterCommitters but I can't seem to be able to edit it, can u add me or give me the needed permissions? My wiki username is FrancoSabadini. Try now. Thanks. Franco - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
On 23 September 2011 18:14, sebb seb...@gmail.com wrote: On 23 September 2011 17:15, Milamber milam...@apache.org wrote: Hello, It's seems all open bugs with 2.5.1RC1 are closed. I will start the RC2 process tomorrow. OK. Just found a problem with the HC4 retries - they prevent StopTest from working. There's a deadlock in the code that prevents the interrupt from working when there is a retry. [At the back of my mind, I thought there was another reason why I set the retry count to 0!] Shutdown works fine, because it does not try to interrupt the sample. I think there's a work-round I can use in the JMeter code, but I don't think we should release the code as is. Sorry. The Java and HC3.1 samplers work fine; it's only HC4 that has the problem. I'll let you know if there's a solution ASAP. I'm working on a new Asynchronous Sample Listener for client-server mode. If I get that finished tonight I'll commit it. I've committed it. It should not cause any other issues as the code is mostly new, and is optional - if there are problems, it does not have to be used. Milamber Le 22/09/2011 22:53, Milamber a ecrit : Hello, The first release candidate for JMeter 2.5.1 has been prepared, and your votes are solicited. This release fixes mainly some bugs appeared since JMeter 2.5, but contains few improvements. Tests (load tests or functional tests) with JVM 5/6/7 on Linux/Windows/Mac OS on functionality changes are welcomes (HttpClient 4.1 request, Http request with parallels embedded resources, View results tree, WebServices (SOAP) request, etc) List of changes: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs/changes.html JMeter is a Java desktop application designed to load test functional behavior and measure performance. The current version is targeted at Java 1.5+. Archives/hashes/sigs and RAT report: http://people.apache.org/~milamber/jmeter-2.5.1RC1/dist MD5 hashes of archives for this vote: c1c63f36692ac2fd2e7cca2f2b162c6e *jakarta-jmeter-2.5.1.tgz 8345f36f769872651d53db2436eac100 *jakarta-jmeter-2.5.1.zip c232ea7259543592f56c2dca7ba5850d *jakarta-jmeter-2.5.1_src.tgz 52a2dee578fd433d286e16dfe928b6b2 *jakarta-jmeter-2.5.1_src.zip Site Docs are here: http://people.apache.org/~milamber/jmeter-2.5.1RC1/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_5_1_RC1 (r1174408) Keys are here: http://svn.apache.org/repos/asf/jakarta/site/dist/jmeter/ also http://people.apache.org/~milamber/ N.B. To download the dependencies: ant download_jars To create the jars and test JMeter: ant package test. JMeter 2.5 requires Java 1.5 or later. Note that there is a bug in Java on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: [java] WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number This does not affect JMeter operation. All feedback (and votes!) welcome. [ ] +1 I support this release [ ] +0 I am OK with this release [ ] -0 OK, but [ ] -1 I do not support this release (please indicate why) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and rename the RC tag as the release tag. Thanks in advance! Milamber - 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 - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
On 23 September 2011 23:17, sebb seb...@gmail.com wrote: On 23 September 2011 18:14, sebb seb...@gmail.com wrote: On 23 September 2011 17:15, Milamber milam...@apache.org wrote: Hello, It's seems all open bugs with 2.5.1RC1 are closed. I will start the RC2 process tomorrow. OK. Just found a problem with the HC4 retries - they prevent StopTest from working. There's a deadlock in the code that prevents the interrupt from working when there is a retry. [At the back of my mind, I thought there was another reason why I set the retry count to 0!] Shutdown works fine, because it does not try to interrupt the sample. I think there's a work-round I can use in the JMeter code, but I don't think we should release the code as is. Sorry. The Java and HC3.1 samplers work fine; it's only HC4 that has the problem. I'll let you know if there's a solution ASAP. URL: http://svn.apache.org/viewvc?rev=1175069view=rev Log: Temporary hack to work round https://issues.apache.org/jira/browse/HTTPCLIENT-1120 Note: copying the code from the patch did not seem to work; it looks like isAborted() was not set. Hopefully that is fixed in 4.1.3 That seems to have fixed it for me, or at least improved matters. Still needs more testing to see if the deadlock I found - reported in https://issues.apache.org/jira/browse/HTTPCLIENT-1127 - can still occur. BTW, I found the deadlock testing against the mirror server. - To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
