You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jakarta.apache.org by Milamber <mi...@apache.org> on 2011/09/23 00:53:48 UTC
[VOTE] Release JMeter 2.5.1 RC1
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-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 23 September 2011 11:29, sebb <se...@gmail.com> wrote:
> 2011/9/23 Stéphane Hoblingre <st...@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 <st...@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 <wo...@gmail.com> wrote:
>>>
>>>> +1
>>>>
>>>> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
>>>> > For additional commands, e-mail: dev-help@jakarta.apache.org
>>>> >
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>>
>>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
2011/9/23 Stéphane Hoblingre <st...@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.
> Regards,
>
> Stef
>
> 2011/9/23 Stéphane Hoblingre <st...@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 <wo...@gmail.com> wrote:
>>
>>> +1
>>>
>>> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
>>> > For additional commands, e-mail: dev-help@jakarta.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Stéphane Hoblingre <st...@gmail.com>.
Great! Thanks!
Stef
On Fri, Sep 23, 2011 at 5:24 PM, sebb <se...@gmail.com> wrote:
> 2011/9/23 Stéphane Hoblingre <st...@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.mouawad@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 <st...@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 <st...@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 <wo...@gmail.com>
> wrote:
> >> > >
> >> > >> +1
> >> > >>
> >> > >> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
> >> > >> > For additional commands, e-mail: dev-help@jakarta.apache.org
> >> > >> >
> >> > >> >
> >> > >>
> >> > >>
> ---------------------------------------------------------------------
> >> > >> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> >> > >> For additional commands, e-mail: dev-help@jakarta.apache.org
> >> > >>
> >> > >>
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Cordialement.
> >> Philippe Mouawad.
> >> Ubik-Ingénierie
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
2011/9/23 Stéphane Hoblingre <st...@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.mouawad@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 <st...@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 <st...@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 <wo...@gmail.com> wrote:
>> > >
>> > >> +1
>> > >>
>> > >> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
>> > >> > For additional commands, e-mail: dev-help@jakarta.apache.org
>> > >> >
>> > >> >
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> > >> For additional commands, e-mail: dev-help@jakarta.apache.org
>> > >>
>> > >>
>> > >
>> >
>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>> Ubik-Ingénierie
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Stéphane Hoblingre <st...@gmail.com>.
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.mouawad@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 <st...@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 <st...@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 <wo...@gmail.com> wrote:
> > >
> > >> +1
> > >>
> > >> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
> > >> > For additional commands, e-mail: dev-help@jakarta.apache.org
> > >> >
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> > >> For additional commands, e-mail: dev-help@jakarta.apache.org
> > >>
> > >>
> > >
> >
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
> Ubik-Ingénierie
>
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Philippe Mouawad <ph...@gmail.com>.
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 <st...@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 <st...@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 <wo...@gmail.com> wrote:
> >
> >> +1
> >>
> >> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: dev-help@jakarta.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: dev-help@jakarta.apache.org
> >>
> >>
> >
>
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Stéphane Hoblingre <st...@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 <st...@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 <wo...@gmail.com> wrote:
>
>> +1
>>
>> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: dev-help@jakarta.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Stéphane Hoblingre <st...@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 <wo...@gmail.com> wrote:
> +1
>
> On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Peter Lin <wo...@gmail.com>.
+1
On Thu, Sep 22, 2011 at 6:53 PM, Milamber <mi...@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-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
2011/9/26 Stéphane Hoblingre <st...@gmail.com>:
> Yes true, the bug happens also with the DummySampler of our plugins (
> http://code.google.com/p/jmeter-plugins/) and appeared from 2.5.1 only.
Not sure that has the same cause; as far as I can tell DummySampler
does not support interrupt(), which is the origin of the deadlocks in
HC4.
Please could you attach a thread dump and jmeter log file to the bug?
> Stef
>
> On Mon, Sep 26, 2011 at 9:18 PM, sebb <se...@gmail.com> wrote:
>
>> On 26 September 2011 09:32, Philippe Mouawad <ph...@gmail.com>
>> wrote:
>> > Hello I attached all infos on ISSUE:
>> >
>> > - Test case
>> > - Log file in DEBUG
>> > - Thread Dump
>> >
>> > Note that I reproduced it every time with what I described in issue.
>>
>> I can also now reproduce the deadlock easily with HC4 and mirror server.
>> I was using a simplified test case that had caused the deadlock prior
>> to my fix, but was not causing the dealock afterwards.
>> This was because it only had one sample - that had been sufficient
>> originally, but was not sufficient later.
>> Sorry, that's my fault; should have stayed with the original test case.
>>
>> The fix I made to HC4 - overriding the retryRequest() method -
>> actually only works for a single sampler, because the "interrupted"
>> variable is fetched from the class instance that was used to create
>> the override. I introduced the "interrupted" variable, because the fix
>> from https://issues.apache.org/jira/browse/HTTPCLIENT-1120 did not
>> seem to work. I need to look at that again. This is needed to stop HC4
>> from retrying aborted requests, which I think is a separate issue from
>> the deadlocks.
>>
>> I now think there's a subtle bug in JMeterThread.
>> I had expected the interrupt to complete, and then the sample to
>> complete, thus the shutdown code would run after the interrupt code.
>> However, it looks as though the sample can complete before the
>> interrupt method returns.
>> This allows the thread to run the shutdown code whilst the interrupt
>> is still in progress.
>>
>> In turn this triggers the deadlock issue in HC4, but could equally
>> cause issues with other samplers.
>> The code needs to ensure that shutdown cannot happen whilst an
>> interrupt is in progress.
>>
>> I'll commit a fix to SVN ASAP.
>>
>> Sorry Milamber, but I think we need to cancel this RC vote.
>>
>> > I also attached a patch that works on my tests.
>> > I let you check.
>> >
>> > Regards
>> > Philippe Mouawad
>> >
>> > On Sun, Sep 25, 2011 at 1:46 PM, sebb <se...@gmail.com> wrote:
>> >
>> >> On 25 September 2011 12:22, sebb <se...@gmail.com> wrote:
>> >> > On 25 September 2011 01:45, Milamber <mi...@apache.org> wrote:
>> >> >>
>> >> >>
>> >> >> Le 25/09/2011 00:08, sebb a ecrit :
>> >> >>> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
>> >> >>>
>> >> >>>>
>> >> >>>> Le 23/09/2011 23:38, sebb a ecrit :
>> >> >>>>
>> >> >>>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
>> >> >>>>> Log:
>> >> >>>>> Temporary hack to work round
>> >> >>>>>
>> >> >>>>>
>> >> >>>> This temporary hack don't always work for me. When I call Stop
>> command
>> >> >>>> at the beginning of a test (before end of ramp up), I have the same
>> >> >>>> deadlock.
>> >> >>>> (but sometimes the stop works fine.)
>> >> >>>>
>> >> >>> Can you do a thread dump when this happens?
>> >> >>>
>> >> >>
>> >> >>
>> >> >> Found one Java-level deadlock:
>> >> >> =============================
>> >> >> "Thread-205":
>> >> >> waiting to lock monitor 0x0000000000d0bf78 (object
>> 0x00000000e2c89ba8,
>> >> >> a org.apache.http.impl.conn.SingleClientConnManager),
>> >> >> which is held by "Thread Group 1-1"
>> >> >> "Thread Group 1-1":
>> >> >> waiting to lock monitor 0x000000000205e638 (object
>> 0x00000000e3425510,
>> >> >> a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
>> >> >> which is held by "Thread-205"
>> >> >>
>> >> >> Java stack information for the threads listed above:
>> >> >> ===================================================
>> >> >> "Thread-205":
>> >> >> at
>> >> >>
>> >>
>> org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
>> >> >> - waiting to lock <0x00000000e2c89ba8> (a
>> >> >> org.apache.http.impl.conn.SingleClientConnManager)
>> >> >> at
>> >> >>
>> >>
>> org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
>> >> >> - locked <0x00000000e3425510> (a
>> >> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
>> >> >> at
>> >> >>
>> >>
>> org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
>> >> >> at
>> >> >>
>> org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
>> >> >> at java.lang.Thread.run(Thread.java:722)
>> >> >> "Thread Group 1-1":
>> >> >> at
>> >> >>
>> >>
>> org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
>> >> >> - waiting to lock <0x00000000e3425510> (a
>> >> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
>> >> >> at
>> >> >>
>> >>
>> org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
>> >> >> - locked <0x00000000e2c89ba8> (a
>> >> >> org.apache.http.impl.conn.SingleClientConnManager)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
>> >> >> at
>> >> >>
>> org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
>> >> >> at
>> >> org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
>> >> >> at
>> >> >>
>> >>
>> org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
>> >> >> at
>> org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
>> >> >> at java.lang.Thread.run(Thread.java:722)
>> >> >>
>> >> >> Found 1 deadlock.
>> >> >>
>> >> >>
>> >> >>
>> >> >> Full thread dump in attachment.
>> >> >
>> >> > Thanks!
>> >> >
>> >> >> Test case is the SimpleTest.jmx, stop after 6-7 VU.
>> >> >> For this thread dump, I wait the end of ramp up for 100 VU, but only
>> 99
>> >> >> up. (the 'last' is the TG 1-1)
>> >> >>
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>>> I thinks we must release the version 2.5.1 to correct the others
>> bugs
>> >> >>>> already fixed, and add a known problem in documentation for this
>> >> deadlook?
>> >> >>>>
>> >> >>> Yes, that sounds reasonable. It's not clear yet whether this is a
>> >> >>> JMeter or HC4 problem; nor is it clear what to do to fix it.
>> >> >>> Anyway, it only occurs sometimes, and it only occurs when trying to
>> >> >>> stop the test - so the GUI can just be exitted.
>> >> >>>
>> >> >>
>> >> >> Ok, I will prepare the RC2 tomorrow.
>> >> >> (Perhaps open a jmeter bugzilla for this bug?)
>> >> >
>> >> > I've opened https://issues.apache.org/jira/browse/HTTPCLIENT-1127 in
>> >> > case the bug is in HC4.
>> >> > Looks like that may have a lock ordering problem.
>> >> >
>> >> > But it may be caused by a bug in the way JMeter processes shutdown;
>> >> > I'm a bit surprised that threadFinished occurs during interrupt
>> >> > processing.
>> >> > I'll raise a JMeter bug and take a further look later today.
>> >>
>> >> Raised https://issues.apache.org/bugzilla/show_bug.cgi?id=51888
>> >>
>> >> I don't suppose you have the corresponding JMeter log file?
>> >> I think we need both dump and log to debug the problem.
>> >>
>> >> If not, never mind, I'll see if I can trigger the fault again.
>> >>
>> >> >
>> >> >> Milamber
>> >> >>
>> >> >>>
>> >> >>>> Milamber
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>> 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-unsubscribe@jakarta.apache.org
>> >> >>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>
>> >> >>>>
>> ---------------------------------------------------------------------
>> >> >>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> >> >>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>
>> ---------------------------------------------------------------------
>> >> >>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> >> >>> For additional commands, e-mail: dev-help@jakarta.apache.org
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail: dev-help@jakarta.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>> > Ubik-Ingénierie
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello Stéphane Hoblinfre,
Can you test with last build, issue you submitted has been fixed.
Regards
Philippe
2011/9/26 Stéphane Hoblingre <st...@gmail.com>
> Yes true, the bug happens also with the DummySampler of our plugins (
> http://code.google.com/p/jmeter-plugins/) and appeared from 2.5.1 only.
>
> Stef
>
> On Mon, Sep 26, 2011 at 9:18 PM, sebb <se...@gmail.com> wrote:
>
> > On 26 September 2011 09:32, Philippe Mouawad <philippe.mouawad@gmail.com
> >
> > wrote:
> > > Hello I attached all infos on ISSUE:
> > >
> > > - Test case
> > > - Log file in DEBUG
> > > - Thread Dump
> > >
> > > Note that I reproduced it every time with what I described in issue.
> >
> > I can also now reproduce the deadlock easily with HC4 and mirror server.
> > I was using a simplified test case that had caused the deadlock prior
> > to my fix, but was not causing the dealock afterwards.
> > This was because it only had one sample - that had been sufficient
> > originally, but was not sufficient later.
> > Sorry, that's my fault; should have stayed with the original test case.
> >
> > The fix I made to HC4 - overriding the retryRequest() method -
> > actually only works for a single sampler, because the "interrupted"
> > variable is fetched from the class instance that was used to create
> > the override. I introduced the "interrupted" variable, because the fix
> > from https://issues.apache.org/jira/browse/HTTPCLIENT-1120 did not
> > seem to work. I need to look at that again. This is needed to stop HC4
> > from retrying aborted requests, which I think is a separate issue from
> > the deadlocks.
> >
> > I now think there's a subtle bug in JMeterThread.
> > I had expected the interrupt to complete, and then the sample to
> > complete, thus the shutdown code would run after the interrupt code.
> > However, it looks as though the sample can complete before the
> > interrupt method returns.
> > This allows the thread to run the shutdown code whilst the interrupt
> > is still in progress.
> >
> > In turn this triggers the deadlock issue in HC4, but could equally
> > cause issues with other samplers.
> > The code needs to ensure that shutdown cannot happen whilst an
> > interrupt is in progress.
> >
> > I'll commit a fix to SVN ASAP.
> >
> > Sorry Milamber, but I think we need to cancel this RC vote.
> >
> > > I also attached a patch that works on my tests.
> > > I let you check.
> > >
> > > Regards
> > > Philippe Mouawad
> > >
> > > On Sun, Sep 25, 2011 at 1:46 PM, sebb <se...@gmail.com> wrote:
> > >
> > >> On 25 September 2011 12:22, sebb <se...@gmail.com> wrote:
> > >> > On 25 September 2011 01:45, Milamber <mi...@apache.org> wrote:
> > >> >>
> > >> >>
> > >> >> Le 25/09/2011 00:08, sebb a ecrit :
> > >> >>> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
> > >> >>>
> > >> >>>>
> > >> >>>> Le 23/09/2011 23:38, sebb a ecrit :
> > >> >>>>
> > >> >>>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
> > >> >>>>>
> > >> >>>>>
> > >> >>>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
> > >> >>>>> Log:
> > >> >>>>> Temporary hack to work round
> > >> >>>>>
> > >> >>>>>
> > >> >>>> This temporary hack don't always work for me. When I call Stop
> > command
> > >> >>>> at the beginning of a test (before end of ramp up), I have the
> same
> > >> >>>> deadlock.
> > >> >>>> (but sometimes the stop works fine.)
> > >> >>>>
> > >> >>> Can you do a thread dump when this happens?
> > >> >>>
> > >> >>
> > >> >>
> > >> >> Found one Java-level deadlock:
> > >> >> =============================
> > >> >> "Thread-205":
> > >> >> waiting to lock monitor 0x0000000000d0bf78 (object
> > 0x00000000e2c89ba8,
> > >> >> a org.apache.http.impl.conn.SingleClientConnManager),
> > >> >> which is held by "Thread Group 1-1"
> > >> >> "Thread Group 1-1":
> > >> >> waiting to lock monitor 0x000000000205e638 (object
> > 0x00000000e3425510,
> > >> >> a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
> > >> >> which is held by "Thread-205"
> > >> >>
> > >> >> Java stack information for the threads listed above:
> > >> >> ===================================================
> > >> >> "Thread-205":
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
> > >> >> - waiting to lock <0x00000000e2c89ba8> (a
> > >> >> org.apache.http.impl.conn.SingleClientConnManager)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
> > >> >> - locked <0x00000000e3425510> (a
> > >> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
> > >> >> at
> > >> >>
> > org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
> > >> >> at java.lang.Thread.run(Thread.java:722)
> > >> >> "Thread Group 1-1":
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
> > >> >> - waiting to lock <0x00000000e3425510> (a
> > >> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
> > >> >> - locked <0x00000000e2c89ba8> (a
> > >> >> org.apache.http.impl.conn.SingleClientConnManager)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
> > >> >> at
> > >> >>
> > org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
> > >> >> at
> > >> org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
> > >> >> at
> > >> >>
> > >>
> >
> org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
> > >> >> at
> > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
> > >> >> at java.lang.Thread.run(Thread.java:722)
> > >> >>
> > >> >> Found 1 deadlock.
> > >> >>
> > >> >>
> > >> >>
> > >> >> Full thread dump in attachment.
> > >> >
> > >> > Thanks!
> > >> >
> > >> >> Test case is the SimpleTest.jmx, stop after 6-7 VU.
> > >> >> For this thread dump, I wait the end of ramp up for 100 VU, but
> only
> > 99
> > >> >> up. (the 'last' is the TG 1-1)
> > >> >>
> > >> >>
> > >> >>>
> > >> >>>
> > >> >>>> I thinks we must release the version 2.5.1 to correct the others
> > bugs
> > >> >>>> already fixed, and add a known problem in documentation for this
> > >> deadlook?
> > >> >>>>
> > >> >>> Yes, that sounds reasonable. It's not clear yet whether this is a
> > >> >>> JMeter or HC4 problem; nor is it clear what to do to fix it.
> > >> >>> Anyway, it only occurs sometimes, and it only occurs when trying
> to
> > >> >>> stop the test - so the GUI can just be exitted.
> > >> >>>
> > >> >>
> > >> >> Ok, I will prepare the RC2 tomorrow.
> > >> >> (Perhaps open a jmeter bugzilla for this bug?)
> > >> >
> > >> > I've opened https://issues.apache.org/jira/browse/HTTPCLIENT-1127in
> > >> > case the bug is in HC4.
> > >> > Looks like that may have a lock ordering problem.
> > >> >
> > >> > But it may be caused by a bug in the way JMeter processes shutdown;
> > >> > I'm a bit surprised that threadFinished occurs during interrupt
> > >> > processing.
> > >> > I'll raise a JMeter bug and take a further look later today.
> > >>
> > >> Raised https://issues.apache.org/bugzilla/show_bug.cgi?id=51888
> > >>
> > >> I don't suppose you have the corresponding JMeter log file?
> > >> I think we need both dump and log to debug the problem.
> > >>
> > >> If not, never mind, I'll see if I can trigger the fault again.
> > >>
> > >> >
> > >> >> Milamber
> > >> >>
> > >> >>>
> > >> >>>> Milamber
> > >> >>>>
> > >> >>>>
> > >> >>>>
> > >> >>>>
> > >> >>>>> 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-unsubscribe@jakarta.apache.org
> > >> >>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
> > >> >>>>>
> > >> >>>>>
> > >> >>>>>
> > >> >>>>>
> > >> >>>>
> > >> >>>>
> > ---------------------------------------------------------------------
> > >> >>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> > >> >>>> For additional commands, e-mail: dev-help@jakarta.apache.org
> > >> >>>>
> > >> >>>>
> > >> >>>>
> > >> >>>
> > ---------------------------------------------------------------------
> > >> >>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> > >> >>> For additional commands, e-mail: dev-help@jakarta.apache.org
> > >> >>>
> > >> >>>
> > >> >>>
> > >> >>
> > >> >>
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> > >> For additional commands, e-mail: dev-help@jakarta.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> > > Ubik-Ingénierie
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: dev-help@jakarta.apache.org
> >
> >
>
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Stéphane Hoblingre <st...@gmail.com>.
Yes true, the bug happens also with the DummySampler of our plugins (
http://code.google.com/p/jmeter-plugins/) and appeared from 2.5.1 only.
Stef
On Mon, Sep 26, 2011 at 9:18 PM, sebb <se...@gmail.com> wrote:
> On 26 September 2011 09:32, Philippe Mouawad <ph...@gmail.com>
> wrote:
> > Hello I attached all infos on ISSUE:
> >
> > - Test case
> > - Log file in DEBUG
> > - Thread Dump
> >
> > Note that I reproduced it every time with what I described in issue.
>
> I can also now reproduce the deadlock easily with HC4 and mirror server.
> I was using a simplified test case that had caused the deadlock prior
> to my fix, but was not causing the dealock afterwards.
> This was because it only had one sample - that had been sufficient
> originally, but was not sufficient later.
> Sorry, that's my fault; should have stayed with the original test case.
>
> The fix I made to HC4 - overriding the retryRequest() method -
> actually only works for a single sampler, because the "interrupted"
> variable is fetched from the class instance that was used to create
> the override. I introduced the "interrupted" variable, because the fix
> from https://issues.apache.org/jira/browse/HTTPCLIENT-1120 did not
> seem to work. I need to look at that again. This is needed to stop HC4
> from retrying aborted requests, which I think is a separate issue from
> the deadlocks.
>
> I now think there's a subtle bug in JMeterThread.
> I had expected the interrupt to complete, and then the sample to
> complete, thus the shutdown code would run after the interrupt code.
> However, it looks as though the sample can complete before the
> interrupt method returns.
> This allows the thread to run the shutdown code whilst the interrupt
> is still in progress.
>
> In turn this triggers the deadlock issue in HC4, but could equally
> cause issues with other samplers.
> The code needs to ensure that shutdown cannot happen whilst an
> interrupt is in progress.
>
> I'll commit a fix to SVN ASAP.
>
> Sorry Milamber, but I think we need to cancel this RC vote.
>
> > I also attached a patch that works on my tests.
> > I let you check.
> >
> > Regards
> > Philippe Mouawad
> >
> > On Sun, Sep 25, 2011 at 1:46 PM, sebb <se...@gmail.com> wrote:
> >
> >> On 25 September 2011 12:22, sebb <se...@gmail.com> wrote:
> >> > On 25 September 2011 01:45, Milamber <mi...@apache.org> wrote:
> >> >>
> >> >>
> >> >> Le 25/09/2011 00:08, sebb a ecrit :
> >> >>> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
> >> >>>
> >> >>>>
> >> >>>> Le 23/09/2011 23:38, sebb a ecrit :
> >> >>>>
> >> >>>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
> >> >>>>>
> >> >>>>>
> >> >>>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
> >> >>>>> Log:
> >> >>>>> Temporary hack to work round
> >> >>>>>
> >> >>>>>
> >> >>>> This temporary hack don't always work for me. When I call Stop
> command
> >> >>>> at the beginning of a test (before end of ramp up), I have the same
> >> >>>> deadlock.
> >> >>>> (but sometimes the stop works fine.)
> >> >>>>
> >> >>> Can you do a thread dump when this happens?
> >> >>>
> >> >>
> >> >>
> >> >> Found one Java-level deadlock:
> >> >> =============================
> >> >> "Thread-205":
> >> >> waiting to lock monitor 0x0000000000d0bf78 (object
> 0x00000000e2c89ba8,
> >> >> a org.apache.http.impl.conn.SingleClientConnManager),
> >> >> which is held by "Thread Group 1-1"
> >> >> "Thread Group 1-1":
> >> >> waiting to lock monitor 0x000000000205e638 (object
> 0x00000000e3425510,
> >> >> a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
> >> >> which is held by "Thread-205"
> >> >>
> >> >> Java stack information for the threads listed above:
> >> >> ===================================================
> >> >> "Thread-205":
> >> >> at
> >> >>
> >>
> org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
> >> >> - waiting to lock <0x00000000e2c89ba8> (a
> >> >> org.apache.http.impl.conn.SingleClientConnManager)
> >> >> at
> >> >>
> >>
> org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
> >> >> - locked <0x00000000e3425510> (a
> >> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> >> >> at
> >> >>
> >>
> org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
> >> >> at
> >> >>
> org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
> >> >> at java.lang.Thread.run(Thread.java:722)
> >> >> "Thread Group 1-1":
> >> >> at
> >> >>
> >>
> org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
> >> >> - waiting to lock <0x00000000e3425510> (a
> >> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> >> >> at
> >> >>
> >>
> org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
> >> >> - locked <0x00000000e2c89ba8> (a
> >> >> org.apache.http.impl.conn.SingleClientConnManager)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
> >> >> at
> >> >>
> org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
> >> >> at
> >> org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
> >> >> at
> >> >>
> >>
> org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
> >> >> at
> org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
> >> >> at java.lang.Thread.run(Thread.java:722)
> >> >>
> >> >> Found 1 deadlock.
> >> >>
> >> >>
> >> >>
> >> >> Full thread dump in attachment.
> >> >
> >> > Thanks!
> >> >
> >> >> Test case is the SimpleTest.jmx, stop after 6-7 VU.
> >> >> For this thread dump, I wait the end of ramp up for 100 VU, but only
> 99
> >> >> up. (the 'last' is the TG 1-1)
> >> >>
> >> >>
> >> >>>
> >> >>>
> >> >>>> I thinks we must release the version 2.5.1 to correct the others
> bugs
> >> >>>> already fixed, and add a known problem in documentation for this
> >> deadlook?
> >> >>>>
> >> >>> Yes, that sounds reasonable. It's not clear yet whether this is a
> >> >>> JMeter or HC4 problem; nor is it clear what to do to fix it.
> >> >>> Anyway, it only occurs sometimes, and it only occurs when trying to
> >> >>> stop the test - so the GUI can just be exitted.
> >> >>>
> >> >>
> >> >> Ok, I will prepare the RC2 tomorrow.
> >> >> (Perhaps open a jmeter bugzilla for this bug?)
> >> >
> >> > I've opened https://issues.apache.org/jira/browse/HTTPCLIENT-1127 in
> >> > case the bug is in HC4.
> >> > Looks like that may have a lock ordering problem.
> >> >
> >> > But it may be caused by a bug in the way JMeter processes shutdown;
> >> > I'm a bit surprised that threadFinished occurs during interrupt
> >> > processing.
> >> > I'll raise a JMeter bug and take a further look later today.
> >>
> >> Raised https://issues.apache.org/bugzilla/show_bug.cgi?id=51888
> >>
> >> I don't suppose you have the corresponding JMeter log file?
> >> I think we need both dump and log to debug the problem.
> >>
> >> If not, never mind, I'll see if I can trigger the fault again.
> >>
> >> >
> >> >> Milamber
> >> >>
> >> >>>
> >> >>>> Milamber
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>> 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-unsubscribe@jakarta.apache.org
> >> >>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>
> >> >>>>
> ---------------------------------------------------------------------
> >> >>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> >> >>>> For additional commands, e-mail: dev-help@jakarta.apache.org
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> >> >>> For additional commands, e-mail: dev-help@jakarta.apache.org
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: dev-help@jakarta.apache.org
> >>
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
> > Ubik-Ingénierie
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 26 September 2011 09:32, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello I attached all infos on ISSUE:
>
> - Test case
> - Log file in DEBUG
> - Thread Dump
>
> Note that I reproduced it every time with what I described in issue.
I can also now reproduce the deadlock easily with HC4 and mirror server.
I was using a simplified test case that had caused the deadlock prior
to my fix, but was not causing the dealock afterwards.
This was because it only had one sample - that had been sufficient
originally, but was not sufficient later.
Sorry, that's my fault; should have stayed with the original test case.
The fix I made to HC4 - overriding the retryRequest() method -
actually only works for a single sampler, because the "interrupted"
variable is fetched from the class instance that was used to create
the override. I introduced the "interrupted" variable, because the fix
from https://issues.apache.org/jira/browse/HTTPCLIENT-1120 did not
seem to work. I need to look at that again. This is needed to stop HC4
from retrying aborted requests, which I think is a separate issue from
the deadlocks.
I now think there's a subtle bug in JMeterThread.
I had expected the interrupt to complete, and then the sample to
complete, thus the shutdown code would run after the interrupt code.
However, it looks as though the sample can complete before the
interrupt method returns.
This allows the thread to run the shutdown code whilst the interrupt
is still in progress.
In turn this triggers the deadlock issue in HC4, but could equally
cause issues with other samplers.
The code needs to ensure that shutdown cannot happen whilst an
interrupt is in progress.
I'll commit a fix to SVN ASAP.
Sorry Milamber, but I think we need to cancel this RC vote.
> I also attached a patch that works on my tests.
> I let you check.
>
> Regards
> Philippe Mouawad
>
> On Sun, Sep 25, 2011 at 1:46 PM, sebb <se...@gmail.com> wrote:
>
>> On 25 September 2011 12:22, sebb <se...@gmail.com> wrote:
>> > On 25 September 2011 01:45, Milamber <mi...@apache.org> wrote:
>> >>
>> >>
>> >> Le 25/09/2011 00:08, sebb a ecrit :
>> >>> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
>> >>>
>> >>>>
>> >>>> Le 23/09/2011 23:38, sebb a ecrit :
>> >>>>
>> >>>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
>> >>>>>
>> >>>>>
>> >>>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>> >>>>>>
>> >>>>>>
>> >>>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
>> >>>>> Log:
>> >>>>> Temporary hack to work round
>> >>>>>
>> >>>>>
>> >>>> This temporary hack don't always work for me. When I call Stop command
>> >>>> at the beginning of a test (before end of ramp up), I have the same
>> >>>> deadlock.
>> >>>> (but sometimes the stop works fine.)
>> >>>>
>> >>> Can you do a thread dump when this happens?
>> >>>
>> >>
>> >>
>> >> Found one Java-level deadlock:
>> >> =============================
>> >> "Thread-205":
>> >> waiting to lock monitor 0x0000000000d0bf78 (object 0x00000000e2c89ba8,
>> >> a org.apache.http.impl.conn.SingleClientConnManager),
>> >> which is held by "Thread Group 1-1"
>> >> "Thread Group 1-1":
>> >> waiting to lock monitor 0x000000000205e638 (object 0x00000000e3425510,
>> >> a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
>> >> which is held by "Thread-205"
>> >>
>> >> Java stack information for the threads listed above:
>> >> ===================================================
>> >> "Thread-205":
>> >> at
>> >>
>> org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
>> >> - waiting to lock <0x00000000e2c89ba8> (a
>> >> org.apache.http.impl.conn.SingleClientConnManager)
>> >> at
>> >>
>> org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
>> >> - locked <0x00000000e3425510> (a
>> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
>> >> at
>> >>
>> org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
>> >> at
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
>> >> at
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
>> >> at
>> >> org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
>> >> at
>> >>
>> org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
>> >> at
>> >>
>> org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
>> >> at
>> >>
>> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
>> >> at java.lang.Thread.run(Thread.java:722)
>> >> "Thread Group 1-1":
>> >> at
>> >>
>> org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
>> >> - waiting to lock <0x00000000e3425510> (a
>> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
>> >> at
>> >>
>> org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
>> >> - locked <0x00000000e2c89ba8> (a
>> >> org.apache.http.impl.conn.SingleClientConnManager)
>> >> at
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
>> >> at
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
>> >> at
>> >>
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
>> >> at
>> >>
>> org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
>> >> at
>> >> org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
>> >> at
>> org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
>> >> at
>> >>
>> org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
>> >> at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
>> >> at java.lang.Thread.run(Thread.java:722)
>> >>
>> >> Found 1 deadlock.
>> >>
>> >>
>> >>
>> >> Full thread dump in attachment.
>> >
>> > Thanks!
>> >
>> >> Test case is the SimpleTest.jmx, stop after 6-7 VU.
>> >> For this thread dump, I wait the end of ramp up for 100 VU, but only 99
>> >> up. (the 'last' is the TG 1-1)
>> >>
>> >>
>> >>>
>> >>>
>> >>>> I thinks we must release the version 2.5.1 to correct the others bugs
>> >>>> already fixed, and add a known problem in documentation for this
>> deadlook?
>> >>>>
>> >>> Yes, that sounds reasonable. It's not clear yet whether this is a
>> >>> JMeter or HC4 problem; nor is it clear what to do to fix it.
>> >>> Anyway, it only occurs sometimes, and it only occurs when trying to
>> >>> stop the test - so the GUI can just be exitted.
>> >>>
>> >>
>> >> Ok, I will prepare the RC2 tomorrow.
>> >> (Perhaps open a jmeter bugzilla for this bug?)
>> >
>> > I've opened https://issues.apache.org/jira/browse/HTTPCLIENT-1127 in
>> > case the bug is in HC4.
>> > Looks like that may have a lock ordering problem.
>> >
>> > But it may be caused by a bug in the way JMeter processes shutdown;
>> > I'm a bit surprised that threadFinished occurs during interrupt
>> > processing.
>> > I'll raise a JMeter bug and take a further look later today.
>>
>> Raised https://issues.apache.org/bugzilla/show_bug.cgi?id=51888
>>
>> I don't suppose you have the corresponding JMeter log file?
>> I think we need both dump and log to debug the problem.
>>
>> If not, never mind, I'll see if I can trigger the fault again.
>>
>> >
>> >> Milamber
>> >>
>> >>>
>> >>>> Milamber
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>> 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-unsubscribe@jakarta.apache.org
>> >>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>> ---------------------------------------------------------------------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> >>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>> >>>>
>> >>>>
>> >>>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> >>> For additional commands, e-mail: dev-help@jakarta.apache.org
>> >>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
> Ubik-Ingénierie
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello I attached all infos on ISSUE:
- Test case
- Log file in DEBUG
- Thread Dump
Note that I reproduced it every time with what I described in issue.
I also attached a patch that works on my tests.
I let you check.
Regards
Philippe Mouawad
On Sun, Sep 25, 2011 at 1:46 PM, sebb <se...@gmail.com> wrote:
> On 25 September 2011 12:22, sebb <se...@gmail.com> wrote:
> > On 25 September 2011 01:45, Milamber <mi...@apache.org> wrote:
> >>
> >>
> >> Le 25/09/2011 00:08, sebb a ecrit :
> >>> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
> >>>
> >>>>
> >>>> Le 23/09/2011 23:38, sebb a ecrit :
> >>>>
> >>>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
> >>>>>
> >>>>>
> >>>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
> >>>>>>
> >>>>>>
> >>>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
> >>>>> Log:
> >>>>> Temporary hack to work round
> >>>>>
> >>>>>
> >>>> This temporary hack don't always work for me. When I call Stop command
> >>>> at the beginning of a test (before end of ramp up), I have the same
> >>>> deadlock.
> >>>> (but sometimes the stop works fine.)
> >>>>
> >>> Can you do a thread dump when this happens?
> >>>
> >>
> >>
> >> Found one Java-level deadlock:
> >> =============================
> >> "Thread-205":
> >> waiting to lock monitor 0x0000000000d0bf78 (object 0x00000000e2c89ba8,
> >> a org.apache.http.impl.conn.SingleClientConnManager),
> >> which is held by "Thread Group 1-1"
> >> "Thread Group 1-1":
> >> waiting to lock monitor 0x000000000205e638 (object 0x00000000e3425510,
> >> a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
> >> which is held by "Thread-205"
> >>
> >> Java stack information for the threads listed above:
> >> ===================================================
> >> "Thread-205":
> >> at
> >>
> org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
> >> - waiting to lock <0x00000000e2c89ba8> (a
> >> org.apache.http.impl.conn.SingleClientConnManager)
> >> at
> >>
> org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
> >> - locked <0x00000000e3425510> (a
> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> >> at
> >>
> org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
> >> at
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
> >> at
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
> >> at
> >> org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
> >> at
> >>
> org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
> >> at
> >>
> org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
> >> at
> >>
> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
> >> at java.lang.Thread.run(Thread.java:722)
> >> "Thread Group 1-1":
> >> at
> >>
> org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
> >> - waiting to lock <0x00000000e3425510> (a
> >> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> >> at
> >>
> org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
> >> - locked <0x00000000e2c89ba8> (a
> >> org.apache.http.impl.conn.SingleClientConnManager)
> >> at
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
> >> at
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
> >> at
> >>
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
> >> at
> >>
> org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
> >> at
> >> org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
> >> at
> org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
> >> at
> >>
> org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
> >> at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
> >> at java.lang.Thread.run(Thread.java:722)
> >>
> >> Found 1 deadlock.
> >>
> >>
> >>
> >> Full thread dump in attachment.
> >
> > Thanks!
> >
> >> Test case is the SimpleTest.jmx, stop after 6-7 VU.
> >> For this thread dump, I wait the end of ramp up for 100 VU, but only 99
> >> up. (the 'last' is the TG 1-1)
> >>
> >>
> >>>
> >>>
> >>>> I thinks we must release the version 2.5.1 to correct the others bugs
> >>>> already fixed, and add a known problem in documentation for this
> deadlook?
> >>>>
> >>> Yes, that sounds reasonable. It's not clear yet whether this is a
> >>> JMeter or HC4 problem; nor is it clear what to do to fix it.
> >>> Anyway, it only occurs sometimes, and it only occurs when trying to
> >>> stop the test - so the GUI can just be exitted.
> >>>
> >>
> >> Ok, I will prepare the RC2 tomorrow.
> >> (Perhaps open a jmeter bugzilla for this bug?)
> >
> > I've opened https://issues.apache.org/jira/browse/HTTPCLIENT-1127 in
> > case the bug is in HC4.
> > Looks like that may have a lock ordering problem.
> >
> > But it may be caused by a bug in the way JMeter processes shutdown;
> > I'm a bit surprised that threadFinished occurs during interrupt
> > processing.
> > I'll raise a JMeter bug and take a further look later today.
>
> Raised https://issues.apache.org/bugzilla/show_bug.cgi?id=51888
>
> I don't suppose you have the corresponding JMeter log file?
> I think we need both dump and log to debug the problem.
>
> If not, never mind, I'll see if I can trigger the fault again.
>
> >
> >> Milamber
> >>
> >>>
> >>>> Milamber
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> 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-unsubscribe@jakarta.apache.org
> >>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> >>>> For additional commands, e-mail: dev-help@jakarta.apache.org
> >>>>
> >>>>
> >>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> >>> For additional commands, e-mail: dev-help@jakarta.apache.org
> >>>
> >>>
> >>>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 25 September 2011 12:22, sebb <se...@gmail.com> wrote:
> On 25 September 2011 01:45, Milamber <mi...@apache.org> wrote:
>>
>>
>> Le 25/09/2011 00:08, sebb a ecrit :
>>> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
>>>
>>>>
>>>> Le 23/09/2011 23:38, sebb a ecrit :
>>>>
>>>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
>>>>>
>>>>>
>>>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
>>>>> Log:
>>>>> Temporary hack to work round
>>>>>
>>>>>
>>>> This temporary hack don't always work for me. When I call Stop command
>>>> at the beginning of a test (before end of ramp up), I have the same
>>>> deadlock.
>>>> (but sometimes the stop works fine.)
>>>>
>>> Can you do a thread dump when this happens?
>>>
>>
>>
>> Found one Java-level deadlock:
>> =============================
>> "Thread-205":
>> waiting to lock monitor 0x0000000000d0bf78 (object 0x00000000e2c89ba8,
>> a org.apache.http.impl.conn.SingleClientConnManager),
>> which is held by "Thread Group 1-1"
>> "Thread Group 1-1":
>> waiting to lock monitor 0x000000000205e638 (object 0x00000000e3425510,
>> a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
>> which is held by "Thread-205"
>>
>> Java stack information for the threads listed above:
>> ===================================================
>> "Thread-205":
>> at
>> org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
>> - waiting to lock <0x00000000e2c89ba8> (a
>> org.apache.http.impl.conn.SingleClientConnManager)
>> at
>> org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
>> - locked <0x00000000e3425510> (a
>> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
>> at
>> org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
>> at
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
>> at
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
>> at
>> org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
>> at java.lang.Thread.run(Thread.java:722)
>> "Thread Group 1-1":
>> at
>> org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
>> - waiting to lock <0x00000000e3425510> (a
>> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
>> at
>> org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
>> - locked <0x00000000e2c89ba8> (a
>> org.apache.http.impl.conn.SingleClientConnManager)
>> at
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
>> at
>> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
>> at
>> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
>> at
>> org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
>> at
>> org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
>> at org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
>> at
>> org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
>> at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
>> at java.lang.Thread.run(Thread.java:722)
>>
>> Found 1 deadlock.
>>
>>
>>
>> Full thread dump in attachment.
>
> Thanks!
>
>> Test case is the SimpleTest.jmx, stop after 6-7 VU.
>> For this thread dump, I wait the end of ramp up for 100 VU, but only 99
>> up. (the 'last' is the TG 1-1)
>>
>>
>>>
>>>
>>>> I thinks we must release the version 2.5.1 to correct the others bugs
>>>> already fixed, and add a known problem in documentation for this deadlook?
>>>>
>>> Yes, that sounds reasonable. It's not clear yet whether this is a
>>> JMeter or HC4 problem; nor is it clear what to do to fix it.
>>> Anyway, it only occurs sometimes, and it only occurs when trying to
>>> stop the test - so the GUI can just be exitted.
>>>
>>
>> Ok, I will prepare the RC2 tomorrow.
>> (Perhaps open a jmeter bugzilla for this bug?)
>
> I've opened https://issues.apache.org/jira/browse/HTTPCLIENT-1127 in
> case the bug is in HC4.
> Looks like that may have a lock ordering problem.
>
> But it may be caused by a bug in the way JMeter processes shutdown;
> I'm a bit surprised that threadFinished occurs during interrupt
> processing.
> I'll raise a JMeter bug and take a further look later today.
Raised https://issues.apache.org/bugzilla/show_bug.cgi?id=51888
I don't suppose you have the corresponding JMeter log file?
I think we need both dump and log to debug the problem.
If not, never mind, I'll see if I can trigger the fault again.
>
>> Milamber
>>
>>>
>>>> Milamber
>>>>
>>>>
>>>>
>>>>
>>>>> 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-unsubscribe@jakarta.apache.org
>>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>
>>>
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 25 September 2011 01:45, Milamber <mi...@apache.org> wrote:
>
>
> Le 25/09/2011 00:08, sebb a ecrit :
>> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
>>
>>>
>>> Le 23/09/2011 23:38, sebb a ecrit :
>>>
>>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
>>>>
>>>>
>>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>>>>>
>>>>>
>>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
>>>> Log:
>>>> Temporary hack to work round
>>>>
>>>>
>>> This temporary hack don't always work for me. When I call Stop command
>>> at the beginning of a test (before end of ramp up), I have the same
>>> deadlock.
>>> (but sometimes the stop works fine.)
>>>
>> Can you do a thread dump when this happens?
>>
>
>
> Found one Java-level deadlock:
> =============================
> "Thread-205":
> waiting to lock monitor 0x0000000000d0bf78 (object 0x00000000e2c89ba8,
> a org.apache.http.impl.conn.SingleClientConnManager),
> which is held by "Thread Group 1-1"
> "Thread Group 1-1":
> waiting to lock monitor 0x000000000205e638 (object 0x00000000e3425510,
> a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
> which is held by "Thread-205"
>
> Java stack information for the threads listed above:
> ===================================================
> "Thread-205":
> at
> org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
> - waiting to lock <0x00000000e2c89ba8> (a
> org.apache.http.impl.conn.SingleClientConnManager)
> at
> org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
> - locked <0x00000000e3425510> (a
> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> at
> org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
> at
> org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
> at
> org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
> at
> org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
> at
> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
> at java.lang.Thread.run(Thread.java:722)
> "Thread Group 1-1":
> at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
> - waiting to lock <0x00000000e3425510> (a
> org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
> at
> org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
> - locked <0x00000000e2c89ba8> (a
> org.apache.http.impl.conn.SingleClientConnManager)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
> at
> org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
> at
> org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
> at
> org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
> at org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
> at
> org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
> at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
> at java.lang.Thread.run(Thread.java:722)
>
> Found 1 deadlock.
>
>
>
> Full thread dump in attachment.
Thanks!
> Test case is the SimpleTest.jmx, stop after 6-7 VU.
> For this thread dump, I wait the end of ramp up for 100 VU, but only 99
> up. (the 'last' is the TG 1-1)
>
>
>>
>>
>>> I thinks we must release the version 2.5.1 to correct the others bugs
>>> already fixed, and add a known problem in documentation for this deadlook?
>>>
>> Yes, that sounds reasonable. It's not clear yet whether this is a
>> JMeter or HC4 problem; nor is it clear what to do to fix it.
>> Anyway, it only occurs sometimes, and it only occurs when trying to
>> stop the test - so the GUI can just be exitted.
>>
>
> Ok, I will prepare the RC2 tomorrow.
> (Perhaps open a jmeter bugzilla for this bug?)
I've opened https://issues.apache.org/jira/browse/HTTPCLIENT-1127 in
case the bug is in HC4.
Looks like that may have a lock ordering problem.
But it may be caused by a bug in the way JMeter processes shutdown;
I'm a bit surprised that threadFinished occurs during interrupt
processing.
I'll raise a JMeter bug and take a further look later today.
> Milamber
>
>>
>>> Milamber
>>>
>>>
>>>
>>>
>>>> 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-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Milamber <mi...@apache.org>.
Le 25/09/2011 00:08, sebb a ecrit :
> On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
>
>>
>> Le 23/09/2011 23:38, sebb a ecrit :
>>
>>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
>>>
>>>
>>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>>>>
>>>>
>>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
>>> Log:
>>> Temporary hack to work round
>>>
>>>
>> This temporary hack don't always work for me. When I call Stop command
>> at the beginning of a test (before end of ramp up), I have the same
>> deadlock.
>> (but sometimes the stop works fine.)
>>
> Can you do a thread dump when this happens?
>
Found one Java-level deadlock:
=============================
"Thread-205":
waiting to lock monitor 0x0000000000d0bf78 (object 0x00000000e2c89ba8,
a org.apache.http.impl.conn.SingleClientConnManager),
which is held by "Thread Group 1-1"
"Thread Group 1-1":
waiting to lock monitor 0x000000000205e638 (object 0x00000000e3425510,
a org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter),
which is held by "Thread-205"
Java stack information for the threads listed above:
===================================================
"Thread-205":
at
org.apache.http.impl.conn.SingleClientConnManager.releaseConnection(SingleClientConnManager.java:258)
- waiting to lock <0x00000000e2c89ba8> (a
org.apache.http.impl.conn.SingleClientConnManager)
at
org.apache.http.impl.conn.AbstractClientConnAdapter.abortConnection(AbstractClientConnAdapter.java:323)
- locked <0x00000000e3425510> (a
org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
at
org.apache.http.client.methods.HttpRequestBase.abort(HttpRequestBase.java:161)
at
org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.interrupt(HTTPHC4Impl.java:1087)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.interrupt(HTTPSamplerProxy.java:77)
at
org.apache.jmeter.threads.JMeterThread.interrupt(JMeterThread.java:580)
at
org.apache.jmeter.engine.StandardJMeterEngine.tellThreadsToStop(StandardJMeterEngine.java:552)
at
org.apache.jmeter.engine.StandardJMeterEngine.access$300(StandardJMeterEngine.java:58)
at
org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run(StandardJMeterEngine.java:284)
at java.lang.Thread.run(Thread.java:722)
"Thread Group 1-1":
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.detach(AbstractPooledConnAdapter.java:106)
- waiting to lock <0x00000000e3425510> (a
org.apache.http.impl.conn.SingleClientConnManager$ConnAdapter)
at
org.apache.http.impl.conn.SingleClientConnManager.shutdown(SingleClientConnManager.java:342)
- locked <0x00000000e2c89ba8> (a
org.apache.http.impl.conn.SingleClientConnManager)
at
org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.closeThreadLocalConnections(HTTPHC4Impl.java:1072)
at
org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.threadFinished(HTTPHC4Impl.java:1061)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.threadFinished(HTTPSamplerProxy.java:71)
at
org.apache.jmeter.threads.JMeterThread$ThreadListenerTraverser.addNode(JMeterThread.java:553)
at
org.apache.jorphan.collections.HashTree.traverseInto(HashTree.java:986)
at org.apache.jorphan.collections.HashTree.traverse(HashTree.java:969)
at
org.apache.jmeter.threads.JMeterThread.threadFinished(JMeterThread.java:528)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:308)
at java.lang.Thread.run(Thread.java:722)
Found 1 deadlock.
Full thread dump in attachment.
Test case is the SimpleTest.jmx, stop after 6-7 VU.
For this thread dump, I wait the end of ramp up for 100 VU, but only 99
up. (the 'last' is the TG 1-1)
>
>
>> I thinks we must release the version 2.5.1 to correct the others bugs
>> already fixed, and add a known problem in documentation for this deadlook?
>>
> Yes, that sounds reasonable. It's not clear yet whether this is a
> JMeter or HC4 problem; nor is it clear what to do to fix it.
> Anyway, it only occurs sometimes, and it only occurs when trying to
> stop the test - so the GUI can just be exitted.
>
Ok, I will prepare the RC2 tomorrow.
(Perhaps open a jmeter bugzilla for this bug?)
Milamber
>
>> Milamber
>>
>>
>>
>>
>>> 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-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
>
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 25 September 2011 01:03, Milamber <mi...@apache.org> wrote:
>
>
> Le 23/09/2011 23:38, sebb a ecrit :
>> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
>>
>>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>>>
>>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
>> Log:
>> Temporary hack to work round
>>
>
> This temporary hack don't always work for me. When I call Stop command
> at the beginning of a test (before end of ramp up), I have the same
> deadlock.
> (but sometimes the stop works fine.)
Can you do a thread dump when this happens?
> I thinks we must release the version 2.5.1 to correct the others bugs
> already fixed, and add a known problem in documentation for this deadlook?
Yes, that sounds reasonable. It's not clear yet whether this is a
JMeter or HC4 problem; nor is it clear what to do to fix it.
Anyway, it only occurs sometimes, and it only occurs when trying to
stop the test - so the GUI can just be exitted.
> Milamber
>
>
>
>> 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-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Milamber <mi...@apache.org>.
Le 23/09/2011 23:38, sebb a ecrit :
> On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
>
>> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>>
>>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=rev
> Log:
> Temporary hack to work round
>
This temporary hack don't always work for me. When I call Stop command
at the beginning of a test (before end of ramp up), I have the same
deadlock.
(but sometimes the stop works fine.)
I thinks we must release the version 2.5.1 to correct the others bugs
already fixed, and add a known problem in documentation for this deadlook?
Milamber
> 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-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 23 September 2011 23:17, sebb <se...@gmail.com> wrote:
> On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
>> On 23 September 2011 17:15, Milamber <mi...@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=1175069&view=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-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 23 September 2011 18:14, sebb <se...@gmail.com> wrote:
> On 23 September 2011 17:15, Milamber <mi...@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-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by sebb <se...@gmail.com>.
On 23 September 2011 17:15, Milamber <mi...@apache.org> wrote:
> Hello,
>
> It's seems all open bugs with 2.5.1RC1 are closed.
> I will start the RC2 process tomorrow.
OK.
I'm working on a new Asynchronous Sample Listener for client-server mode.
If I get that finished tonight I'll commit 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-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: dev-help@jakarta.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org
Re: [VOTE] Release JMeter 2.5.1 RC1
Posted by Milamber <mi...@apache.org>.
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-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: dev-help@jakarta.apache.org