Jenkins build is back to normal : JMeter Windows #1148

[Apache Jenkins Server]

See 

buildbot success in on jmeter-trunk

[buildbot]

The Buildbot has detected a restored build on builder jmeter-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/3968

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave1_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1841387
Blamelist: pmouawad

Build succeeded!

Sincerely,
 -The Buildbot

buildbot failure in on jmeter-trunk

[buildbot]

The Buildbot has detected a new failure on builder jmeter-trunk while building 
. Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/3967

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb_slave1_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1841386
Blamelist: pmouawad

BUILD FAILED: failed shell_3

Sincerely,
 -The Buildbot

[GitHub] jmeter pull request #399: Fix undefined disabled icon

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/399


---

Re: JMeter send double requests when configure proxy with authentication

[Philippe Mouawad]

Hello Artem,
At minimum, we should have a JMX Test plan that allows testing all
combinations of an authentication using httpbin.org for example and some
java library that could play the role of a proxy, I see the following cases
but feel free to complete:

   - No proxy set
   - Global Proxy set at JMeter level
   - Proxy set in HTTP Request Defaults
   - Proxy set only on request

We should have 2 threads (to check ), 2 iterations and 3 requests (the one
we are concerned about in the middle)

Regarding JUnit, unless  we externalize this particular piece of code into
a custom class, it looks to me hard to do that but if you have an idea ...

Regards

On Wed, Sep 19, 2018 at 5:23 PM Artem Fedorov 
wrote:

> Hi Philippe
>
> I have very simple use case
> I configure squid proxy with authentication and I have jmx Test Plan that
> makes 3 HTTP Request.
>
> I attached jmx file and access log from squid.
>
> Is there any ways for create a JUnit test with the same scenario?
> Also I want to remove !isDynamicProxy(getProxyHost(), getProxyPortInt())) from
> this condition
> ,
> because it always false, when proxy config was specified.
>
> Thanks,
> Artem
>
>
> On Sun, Sep 16, 2018 at 9:53 PM, Philippe Mouawad <
> philippe.moua...@gmail.com> wrote:
>
>> Thanks for last PR update.
>> We'll merge it once 5.0 is released;
>>
>> But before, could you describe the use case met that made you see this
>> issue ?
>> Is the a possibility to provide  a JMX Test plan that could be used as
>> integration test ? and if possible a JUnit test ?
>>
>> Thanks
>>
>> On Sat, Sep 1, 2018 at 4:02 PM Philippe Mouawad <
>> philippe.moua...@gmail.com>
>> wrote:
>>
>> > Hello,
>> > Thanks for latest updates of PR.
>> > 1/ I would not use Object but AuthState instead.
>> >
>> > 2/ Shouldn't we use HTTPCLIENTS_CACHE_PER_THREAD_AND_HTTPCLIENTKEY and
>> > store AuthState there (transforming Pair to Triple)?
>> >
>> > This would be the case for a Thread representing a Virtual User.
>> > But it would not be correct if a thread is not a Virtual User
>> >
>> >
>> > Regards
>> >
>> > On Wed, Aug 29, 2018 at 11:14 AM Artem Fedorov <
>> > artem.fedo...@blazemeter.com> wrote:
>> >
>> >> Fixed.
>> >>
>> >> Regarding (HttpClientContext.PROXY_AUTH_STATE + this) I also have
>> doubts:
>> >>
>> >> - minimal number of authstate, that we should store = Number of
>> Requests
>> >> in
>> >> Test Plan. (each request can use own proxy). Does the AuthState is
>> Thread
>> >> Safe and we can share it between threads? I think no and it'll better
>> to
>> >> store Number of Requests in Plan * Number of Threads AuthStates.
>> >>
>> >> - Also in case if we use dynamic proxy we can not reuse saved
>> AuthState:
>> >>
>> >> >  if (!isDynamicProxy(getProxyHost(), getProxyPortInt())) {
>> >> >localContext.setAttribute(HttpClientContext.PROXY_AUTH_STATE,
>> proxy);
>> >> >  }
>> >>
>> >> Artem
>> >>
>> >> On Tue, Aug 28, 2018 at 11:46 PM, Philippe Mouawad <
>> >> philippe.moua...@gmail.com> wrote:
>> >>
>> >> > Thank you Artem,
>> >> >
>> >> > I made a little comment on PR.
>> >> >
>> >> > Just to be sure I understand the PR:
>> >> >
>> >> >- You set HttpClientContext.PROXY_AUTH_STATE so that it is used if
>> >> >updated
>> >> >
>> >> > But is it correct to store it as:
>> >> >
>> >> >- "http.auth.proxy-scope" + this
>> >> >
>> >> > Because we'll end per Thread with :
>> >> >
>> >> >- Number of Requests in Plan * Number of Threads AuthStates
>> >> >
>> >> > Regards
>> >> >
>> >> >
>> >> > On Mon, Aug 27, 2018 at 3:43 PM Artem Fedorov <
>> >> > artem.fedo...@blazemeter.com>
>> >> > wrote:
>> >> >
>> >> > > Hi Philippe
>> >> > >
>> >> > > https://github.com/apache/jmeter/pull/397
>> >> > >
>> >> > > Let's discuss the details in the PR
>> >> > >
>> >> > > Thanks,
>> >> > > Artem
>> >> > >
>> >> > > On Sun, Aug 26, 2018 at 12:04 AM, Philippe Mouawad <
>> >> > > philippe.moua...@gmail.com> wrote:
>> >> > >
>> >> > > > Hello Artem,
>> >> > > > Go ahead and propose a patch or PR.
>> >> > > > It will be a clearer base to discuss.
>> >> > > >
>> >> > > > Thank you
>> >> > > >
>> >> > > > On Wed, Aug 22, 2018 at 10:56 AM Artem Fedorov <
>> >> > > > artem.fedo...@blazemeter.com>
>> >> > > > wrote:
>> >> > > >
>> >> > > > > I work with the latest JMeter version from github
>> >> > > > > (revision f27c31590cf07bc8427663b62fc22d6d650b95af)
>> >> > > > >
>> >> > > > > I create a Thread Group with 1 loop and 1 user. This Thread
>> Group
>> >> > > > contains
>> >> > > > > View Results Tree (Listener) and HTTP Resuest (Sampler)
>> >> > > > >
>> >> > > > > Configuration of HTTP Sampler:
>> >> > > > >
>> >> > > > > > >> > > > > > testclass="HTTPSamplerProxy" testname="HTTP Request"
>> >> > enabled="true">
>> >> > > > > >   > >> > > > > > elementType="Arguments" guiclass="HTTPArgumentsPanel"
>> >> > > 

Re: JMeter send double requests when configure proxy with authentication

[Artem Fedorov]

Hi Philippe

I have very simple use case
I configure squid proxy with authentication and I have jmx Test Plan that
makes 3 HTTP Request.

I attached jmx file and access log from squid.

Is there any ways for create a JUnit test with the same scenario?
Also I want to remove !isDynamicProxy(getProxyHost(), getProxyPortInt())) from
this condition
,
because it always false, when proxy config was specified.

Thanks,
Artem


On Sun, Sep 16, 2018 at 9:53 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> Thanks for last PR update.
> We'll merge it once 5.0 is released;
>
> But before, could you describe the use case met that made you see this
> issue ?
> Is the a possibility to provide  a JMX Test plan that could be used as
> integration test ? and if possible a JUnit test ?
>
> Thanks
>
> On Sat, Sep 1, 2018 at 4:02 PM Philippe Mouawad <
> philippe.moua...@gmail.com>
> wrote:
>
> > Hello,
> > Thanks for latest updates of PR.
> > 1/ I would not use Object but AuthState instead.
> >
> > 2/ Shouldn't we use HTTPCLIENTS_CACHE_PER_THREAD_AND_HTTPCLIENTKEY and
> > store AuthState there (transforming Pair to Triple)?
> >
> > This would be the case for a Thread representing a Virtual User.
> > But it would not be correct if a thread is not a Virtual User
> >
> >
> > Regards
> >
> > On Wed, Aug 29, 2018 at 11:14 AM Artem Fedorov <
> > artem.fedo...@blazemeter.com> wrote:
> >
> >> Fixed.
> >>
> >> Regarding (HttpClientContext.PROXY_AUTH_STATE + this) I also have
> doubts:
> >>
> >> - minimal number of authstate, that we should store = Number of Requests
> >> in
> >> Test Plan. (each request can use own proxy). Does the AuthState is
> Thread
> >> Safe and we can share it between threads? I think no and it'll better to
> >> store Number of Requests in Plan * Number of Threads AuthStates.
> >>
> >> - Also in case if we use dynamic proxy we can not reuse saved AuthState:
> >>
> >> >  if (!isDynamicProxy(getProxyHost(), getProxyPortInt())) {
> >> >localContext.setAttribute(HttpClientContext.PROXY_AUTH_STATE,
> proxy);
> >> >  }
> >>
> >> Artem
> >>
> >> On Tue, Aug 28, 2018 at 11:46 PM, Philippe Mouawad <
> >> philippe.moua...@gmail.com> wrote:
> >>
> >> > Thank you Artem,
> >> >
> >> > I made a little comment on PR.
> >> >
> >> > Just to be sure I understand the PR:
> >> >
> >> >- You set HttpClientContext.PROXY_AUTH_STATE so that it is used if
> >> >updated
> >> >
> >> > But is it correct to store it as:
> >> >
> >> >- "http.auth.proxy-scope" + this
> >> >
> >> > Because we'll end per Thread with :
> >> >
> >> >- Number of Requests in Plan * Number of Threads AuthStates
> >> >
> >> > Regards
> >> >
> >> >
> >> > On Mon, Aug 27, 2018 at 3:43 PM Artem Fedorov <
> >> > artem.fedo...@blazemeter.com>
> >> > wrote:
> >> >
> >> > > Hi Philippe
> >> > >
> >> > > https://github.com/apache/jmeter/pull/397
> >> > >
> >> > > Let's discuss the details in the PR
> >> > >
> >> > > Thanks,
> >> > > Artem
> >> > >
> >> > > On Sun, Aug 26, 2018 at 12:04 AM, Philippe Mouawad <
> >> > > philippe.moua...@gmail.com> wrote:
> >> > >
> >> > > > Hello Artem,
> >> > > > Go ahead and propose a patch or PR.
> >> > > > It will be a clearer base to discuss.
> >> > > >
> >> > > > Thank you
> >> > > >
> >> > > > On Wed, Aug 22, 2018 at 10:56 AM Artem Fedorov <
> >> > > > artem.fedo...@blazemeter.com>
> >> > > > wrote:
> >> > > >
> >> > > > > I work with the latest JMeter version from github
> >> > > > > (revision f27c31590cf07bc8427663b62fc22d6d650b95af)
> >> > > > >
> >> > > > > I create a Thread Group with 1 loop and 1 user. This Thread
> Group
> >> > > > contains
> >> > > > > View Results Tree (Listener) and HTTP Resuest (Sampler)
> >> > > > >
> >> > > > > Configuration of HTTP Sampler:
> >> > > > >
> >> > > > >  >> > > > > > testclass="HTTPSamplerProxy" testname="HTTP Request"
> >> > enabled="true">
> >> > > > > >>> > > > > > elementType="Arguments" guiclass="HTTPArgumentsPanel"
> >> > > > > testclass="Arguments"
> >> > > > > > testname="User Defined Variables" enabled="true">
> >> > > > > > 
> >> > > > > >   
> >> > > > > >   
> >> > > > > >   
> >> > > > > >stringProp>
> >> > > > > >>> > > name="HTTPSampler.contentEncoding">
> >> > > > > >   
> >> http://blazedemo.com
> >> > > > > > 
> >> > > > > >   GET<
> /stringProp>
> >> > > > > >   true
> >> > > > > >>> > > name="HTTPSampler.auto_redirects">false
> >> > > > > >   true
> >> > > > > >   false >> > > > boolProp>
> >> > > > > >>> > > name="HTTPSampler.embedded_url_re">
> >> > > > > >   
> >> > > > localhost
> >> > > > > >   
> >> > 3321
> >> > > > > >   
> >> > artem
> >> > > > > >   
> >> > artem
> >> > > > > >>> > > 

Build failed in Jenkins: JMeter Windows #1147

[Apache Jenkins Server]

See 


Changes:

[milamber] Next dev version (5.1-SNAPSHOT)

[pmouawad] Switch to HTTPS

[milamber] Prepare next release 5.0: update docs tree and overview (RC2)

[milamber] Fix a litte issue with an unnecessary <

--
[...truncated 193.16 KB...]
 [echo] Starting JDBC_TESTS with file JDBC_TESTS.jmx using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/log4j-slf4j-impl-2.11.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/opt/activemq-all-5.15.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
explanation.
   [jmeter] SLF4J: Actual binding is of type 
[org.apache.logging.slf4j.Log4jLoggerFactory]
   [jmeter] Creating summariser 
   [jmeter] Created the tree successfully using testfiles/JDBC_TESTS.jmx
   [jmeter] Starting the test @ Wed Sep 19 07:23:12 UTC 2018 (1537341792653)
   [jmeter] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 
4445
   [jmeter] summary = 21 in 00:00:02 =   11.9/s Avg:38 Min: 0 Max:  
 764 Err: 0 (0.00%)
   [jmeter] Tidying up ...@ Wed Sep 19 07:23:15 UTC 2018 (1537341795935)
   [jmeter] ... end of run
   [concat] 2018-09-19 07:23:15,912 ERROR o.a.j.t.JMeterThread: Error while 
processing sampler: 'JDBC_With_Failing_PreProcessor'.
   [concat] java.lang.IllegalArgumentException: Variable Name must not be null 
in JDBC PreProcessor
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.AbstractJDBCProcessor.process(AbstractJDBCProcessor.java:45)
 ~[ApacheJMeter_jdbc.jar:r1841290]
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.JDBCPreProcessor.process(JDBCPreProcessor.java:33)
 ~[ApacheJMeter_jdbc.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.runPreProcessors(JMeterThread.java:935) 
~[ApacheJMeter_core.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:537)
 ~[ApacheJMeter_core.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486) 
[ApacheJMeter_core.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253) 
[ApacheJMeter_core.jar:r1841290]
   [concat] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
   [concat] 2018-09-19 07:23:15,921 ERROR o.a.j.t.JMeterThread: Error while 
processing sampler: 'JDBC_With_Failing_PostProcessor'.
   [concat] java.lang.IllegalArgumentException: Variable Name must not be null 
in JDBC PostProcessor
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.AbstractJDBCProcessor.process(AbstractJDBCProcessor.java:45)
 ~[ApacheJMeter_jdbc.jar:r1841290]
   [concat] at 
org.apache.jmeter.protocol.jdbc.processor.JDBCPostProcessor.process(JDBCPostProcessor.java:33)
 ~[ApacheJMeter_jdbc.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.runPostProcessors(JMeterThread.java:925) 
~[ApacheJMeter_core.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:564)
 ~[ApacheJMeter_core.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:486) 
[ApacheJMeter_core.jar:r1841290]
   [concat] at 
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:253) 
[ApacheJMeter_core.jar:r1841290]
   [concat] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
   [concat] 2018-09-19 07:23:15,922 WARN o.a.j.p.j.p.AbstractJDBCProcessor: SQL 
Problem in JDBC PreProcessor: java.sql.SQLSyntaxErrorException: unexpected 
token: USERS
   [concat] 2018-09-19 07:23:15,930 WARN o.a.j.p.j.p.AbstractJDBCProcessor: SQL 
Problem in JDBC PostProcessor: java.sql.SQLSyntaxErrorException: unexpected 
token: USERS
 [echo] JDBC_TESTS output files compared OK

batchtest:
 [echo] Starting JMS_TESTS with file JMS_TESTS.jmx using -X -Jdummy=dummy
   [jmeter] SLF4J: Class path contains multiple SLF4J bindings.
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/log4j-slf4j-impl-2.11.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: Found binding in 
[jar:file:/F:/jenkins/jenkins-slave/workspace/JMeter%20Windows/trunk/lib/opt/activemq-all-5.15.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
   [jmeter] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
explanation.
   [jmeter] SLF4J: Actual binding is of type 
[org.apache.logging.slf4j.Log4jLoggerFactory]
   [jmeter] Creating summariser 
   [jmeter] Created the tree successfully using testfiles/JMS_TESTS.jmx

Jenkins build is back to normal : JMeter-trunk #6906

[Apache Jenkins Server]

See 

[Jmeter Wiki] Update of "FrontPage" by Milamber

[Apache Wiki]

Dear Wiki user,

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

The "FrontPage" page has been changed by Milamber:
https://wiki.apache.org/jmeter/FrontPage?action=diff=176=177

  #pragma section-numbers off
  = Apache JMeter Wiki =
  
||[[http://jmeter.apache.org/|{{http://jmeter.apache.org/images/jmeter.png|http://jmeter.apache.org/|height="77",width="227"}}]]
 ||'''Apache JMeter''' is a 100% pure Java desktop application designed to load 
test functional behavior and measure performance. It was originally designed 
for testing Web Applications but has since expanded to other test functions. ||
- ||'''Current Version:''' 4.0 
||[[http://jmeter.apache.org/download_jmeter.cgi|Download]] 
[[http://issues.apache.org/bugzilla/|JMeter Bugzilla]] 
[[http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW_status=ASSIGNED_status=REOPENED=JMeter|Open
 JMeter Bugs]] [[http://jmeter.apache.org//mail2.html|Mailing Lists]] ||
+ ||'''Current Version:''' 5.0 
||[[http://jmeter.apache.org/download_jmeter.cgi|Download]] 
[[http://issues.apache.org/bugzilla/|JMeter Bugzilla]] 
[[http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW_status=ASSIGNED_status=REOPENED=JMeter|Open
 JMeter Bugs]] [[http://jmeter.apache.org//mail2.html|Mailing Lists]] ||
  
  
  {{{#!wiki red/solid

[ANNOUNCE] Apache JMeter 5.0 released

[Milamber]

The Apache JMeter team is pleased to announce the availability of Apache 
JMeter 5.0 (r1840935).


This release brings a lot of new features and improvements, and also 
fixes bugs.


You can read the New and Noteworthy section with some screenshots to
illustrate improvements and full list of changes at:
http://jmeter.apache.org/changes.html

JMeter 5.0 requires Java 8+ to run.

== All users are highly recommended to upgrade  ==

The Apache JMeter application is a 100% pure Java application designed 
to test server applications.

It can be used to:
   * generate test loads
   * measure performance.
   * test functional behavior
It includes support for protocols such as HTTP(S), JDBC, JMS, FTP, LDAP, 
TCP, native calls and others.

It can also be easily extended with user-written code.

See http://jmeter.apache.org/

Users are highly encouraged to read the JMeter Best Practices section:
http://jmeter.apache.org/usermanual/best-practices.html

The release can be downloaded from:
http://jmeter.apache.org/download_jmeter.cgi

When downloading, please verify signatures using the KEYS file:
https://www.apache.org/dist/jmeter/KEYS


Only the binary archive is needed to run JMeter - there is no need to
download the source archive.

However there are some optional libraries which are not included.
See the "Getting Started" page for details:
http://jmeter.apache.org/usermanual/get-started.html

JMeter artifacts can be downloaded on Maven Central :
  org.apache.jmeter
  ApacheJMeter
  5.0


Enjoy!
The JMeter team

---
https://twitter.com/ApacheJMeter