Re: increase Ram allocation - heap size Jmeter

2019-02-20 Thread Felix Schumacher



Am 18. Februar 2019 10:18:28 MEZ schrieb Prateek Dua :
>Hi Felix,
>
>Just couple of questions here..,
>
>*"**setenv.sh"* includes single line export HEAP="-Xms2g -Xmx2g
>-XX:MaxMetaspaceSize=256m" & if we are increasing from 1gb to 2gb here
>, do
>we have to change the value of MaxMetaspaceSize also from
>-XX:MaxMetaspaceSize=256m
>to -*XX:MaxMetaspaceSize=2g  ?*

Why would you want to do this? 

>
>OR  below lines..
>
>  #!/bin/sh
>  JVM_ARGS="-Xms512m -Xmx5120m"

Memory setting is very dependent on the type of load you have, so we can't give 
general advice. 

You have to look at the amount of memory used and the number and duration of 
the garbage collections. 

Felix 

>
>
>
>
>
>
>
>
>
>
>
>
>
>On Sat, Feb 16, 2019 at 5:35 PM Felix Schumacher <
>felix.schumac...@internetallee.de> wrote:
>
>>
>> Am 16.02.19 um 09:42 schrieb Prateek Dua:
>> > Hi,
>> >
>> > I'm running jmeter via shell script - Jenkins
>> > /var/lib/jenkins/workspace/apache-jmeter-4.0/bin/*jmeter  *
>> >
>> > I want to increase heap size -Xms1g -Xmx1g  in Jmeter as while
>running a
>> > script with heavy csv records got error  [StandardJMeterEngine]
>ERROR
>> > org.apache.jmeter.JMeter - Uncaught exception:
>> > java.lang.OutOfMemoryError: Java heap space
>> >
>> > Have gone through various articles & got confused in changing the
>> > allocation size . There are *3 files in bin folder* which includes
>heap
>> > size allocation config
>> >
>> > 1.   setenv.sh   -- Shell Script
>>
>> This is in my opinion the best place to put your personalized
>settings.
>> Have a look in the docs or in the jmeter script for the variable
>names
>> and set those in the setenv.sh file.
>>
>> That way you can easily update your JMeter installation later.
>>
>> > 2.   *jmeter  --  Unix Executable*   // I'm using this file in
>running
>> > jmeter via shell script from Jenkins as stated above
>> > 3jmeter.sh -- Shell Script
>> >
>> > So my ask is -- Do I have to change the heap size allocation in all
>> these 3
>> > files to see the impact *OR* in any one of these files* OR* only in
>> > jmeter  *jmeter
>> > --  Unix Executable *which I'm using to run Jmeter.
>>
>> You should set the variable in setenv.sh. The other scripts will use
>> those values.
>>
>> Regards,
>>
>>   Felix
>>
>> >
>> >
>> > please help me on this.
>> >
>> > Thanks,
>> > Prateek
>> >
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>
>>

-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org



what??s will happen if httpclient.reset_state_on_thread_group_iteration= true or false

2019-02-20 Thread 1336230737
hello 
  i saw this sentence:

Since JMeter 5.0, when using default HC4 Implementation, JMeter will reset HTTP 
state (SSL State + Connections) on each thread group iteration. If you don't 
want this behaviour, set httpclient.reset_state_on_thread_group_iteration=false
 . i want to know  set httpclient.reset_state_on_thread_group_iteration=true or 
false ??What's going to happen??


 when i  set keepalive =false ??i found The result of Jmeter4.0 is the same as 
that of Jmeter5.0  .no   matter 
httpclient.reset_state_on_thread_group_iteration=false  or true .


but  when i  set keepalive =true??if 
httpclient.reset_state_on_thread_group_iteration=false The result of Jmeter4.0 
is the same as that of Jmeter5.0  . if 
httpclient.reset_state_on_thread_group_iteration=true ??The result of 4.0 is 
different from that of 5.0

RE: The Travis CI build failed

2019-02-20 Thread Sanjay Chaurasia
Dear Philippe/Felix

If this one is a flaxy test and fails sometime. This means we can go ahead with 
PR as Travis CI build had passed earlier for same PR.

Our team is working on the following bug and we have created PRs for the same.
Kindly consider these PRs and let me know if any further information is 
required.

https://bz.apache.org/bugzilla/show_bug.cgi?id=63130 ( PR : 
https://github.com/apache/jmeter/pull/440 )
https://bz.apache.org/bugzilla/show_bug.cgi?id=63129  (PR:  
https://github.com/apache/jmeter/pull/441 )

Thanks and Regards,
Sanjay Chaurasia


-Original Message-
From: Philippe Mouawad [mailto:philippe.moua...@gmail.com] 
Sent: Thursday, February 21, 2019 1:42 AM
To: JMeter Users List 
Subject: Re: The Travis CI build failed

Hi Felix,
Yes this one is flaky.

Regards

On Wednesday, February 20, 2019, Felix Schumacher < 
felix.schumac...@internetallee.de> wrote:

>
> Am 20.02.19 um 07:44 schrieb Sanjay Chaurasia:
>
>> Dear Felix,
>>
>> Thank you so much for your support. Now it's working.
>>
>> But, now I am getting different error.
>>
>> Please find the below link for full log.
>>
>> https://travis-ci.org/apache/jmeter/jobs/495836409
>>
>
> I think again, you are experiencing a test, that sometimes fails (am I 
> right this time, Philippe?).
>
> Felix
>
>
>>
>> Thanks and Regards,
>> Sanjay Chaurasia
>>
>>
>> -Original Message-
>> From: Felix Schumacher [mailto:felix.schumac...@internetallee.de]
>> Sent: Wednesday, February 20, 2019 2:27 AM
>> To: user@jmeter.apache.org
>> Subject: Re: The Travis CI build failed
>>
>>
>> Am 19.02.19 um 21:32 schrieb Felix Schumacher:
>>
>>> Am 19.02.19 um 21:13 schrieb Philippe Mouawad:
>>>
 Hi Felix,
 Are you sure this one is frequent ?

 KeepAlive is ,but I don't remember this one occurred recently.

>>> They all look the same to me ;) but I will have a look.
>>>
>>> In my mail archives I found at least four test runs that were 
>>> affected. I probably deleted quite a few more.
>>>
>>> The last that I found in my archive is from 08.09.2018.
>>>
>>> On the other hand travis seems to be relatively unaffected by that 
>>> test, so I will do a test run of that branch locally.
>>>
>> Hm, it fails locally, too. Now I am letting it run without the 
>> changes of pr/440.
>>
>> And that fails, too.
>>
>> Calling the test plan from the GUI, it reveals that the redirect has 
>> changed to https://... (it was expectedt to be http://)
>>
>> Will commit a change before going to sleep.
>>
>> Felix
>>
>> Felix
>>>
>>> Regards

 On Tue, Feb 19, 2019 at 9:10 PM Felix Schumacher < 
 felix.schumac...@internetallee.de> wrote:

 Am 19.02.19 um 07:50 schrieb Sanjay Chaurasia:
>
>> Hi team.
>>
>> I have created a pull request
>> https://github.com/apache/jmeter/pull/440
>>
> .
>
>> Earlier, the result of Travis CI build was success but now it is 
>> getting
>>
> failed even though I did not make any changes.
>
>> Please find the below link for full log.
>>
>> https://travis-ci.org/apache/jmeter/jobs/494787174
>>
> The reported error is a flaky test, that haunts us for quite a 
> long time now. It has most probably nothing to do with your test case.
>
> Felix
>
>
> Please let me know to resolve the same. I will be highly grateful
>> to you.
>>
>> Thanks and Regards,
>> Sanjay Chaurasia
>>
>>
>> -
>> ---
> - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>
> --
> ---
>>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>>
>>> 
>>> -
>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>

--
Cordialement.
Philippe Mouawad.


Re: The Travis CI build failed

2019-02-20 Thread Philippe Mouawad
Hi Felix,
Yes this one is flaky.

Regards

On Wednesday, February 20, 2019, Felix Schumacher <
felix.schumac...@internetallee.de> wrote:

>
> Am 20.02.19 um 07:44 schrieb Sanjay Chaurasia:
>
>> Dear Felix,
>>
>> Thank you so much for your support. Now it's working.
>>
>> But, now I am getting different error.
>>
>> Please find the below link for full log.
>>
>> https://travis-ci.org/apache/jmeter/jobs/495836409
>>
>
> I think again, you are experiencing a test, that sometimes fails (am I
> right this time, Philippe?).
>
> Felix
>
>
>>
>> Thanks and Regards,
>> Sanjay Chaurasia
>>
>>
>> -Original Message-
>> From: Felix Schumacher [mailto:felix.schumac...@internetallee.de]
>> Sent: Wednesday, February 20, 2019 2:27 AM
>> To: user@jmeter.apache.org
>> Subject: Re: The Travis CI build failed
>>
>>
>> Am 19.02.19 um 21:32 schrieb Felix Schumacher:
>>
>>> Am 19.02.19 um 21:13 schrieb Philippe Mouawad:
>>>
 Hi Felix,
 Are you sure this one is frequent ?

 KeepAlive is ,but I don't remember this one occurred recently.

>>> They all look the same to me ;) but I will have a look.
>>>
>>> In my mail archives I found at least four test runs that were
>>> affected. I probably deleted quite a few more.
>>>
>>> The last that I found in my archive is from 08.09.2018.
>>>
>>> On the other hand travis seems to be relatively unaffected by that
>>> test, so I will do a test run of that branch locally.
>>>
>> Hm, it fails locally, too. Now I am letting it run without the changes of
>> pr/440.
>>
>> And that fails, too.
>>
>> Calling the test plan from the GUI, it reveals that the redirect has
>> changed to https://... (it was expectedt to be http://)
>>
>> Will commit a change before going to sleep.
>>
>> Felix
>>
>> Felix
>>>
>>> Regards

 On Tue, Feb 19, 2019 at 9:10 PM Felix Schumacher <
 felix.schumac...@internetallee.de> wrote:

 Am 19.02.19 um 07:50 schrieb Sanjay Chaurasia:
>
>> Hi team.
>>
>> I have created a pull request
>> https://github.com/apache/jmeter/pull/440
>>
> .
>
>> Earlier, the result of Travis CI build was success but now it is
>> getting
>>
> failed even though I did not make any changes.
>
>> Please find the below link for full log.
>>
>> https://travis-ci.org/apache/jmeter/jobs/494787174
>>
> The reported error is a flaky test, that haunts us for quite a long
> time now. It has most probably nothing to do with your test case.
>
> Felix
>
>
> Please let me know to resolve the same. I will be highly grateful
>> to you.
>>
>> Thanks and Regards,
>> Sanjay Chaurasia
>>
>>
>> 
> - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>
> -
>>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>>
>>> -
>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>

-- 
Cordialement.
Philippe Mouawad.


Re: The Travis CI build failed

2019-02-20 Thread Felix Schumacher



Am 20.02.19 um 07:44 schrieb Sanjay Chaurasia:

Dear Felix,

Thank you so much for your support. Now it's working.

But, now I am getting different error.

Please find the below link for full log.

https://travis-ci.org/apache/jmeter/jobs/495836409


I think again, you are experiencing a test, that sometimes fails (am I 
right this time, Philippe?).


Felix




Thanks and Regards,
Sanjay Chaurasia


-Original Message-
From: Felix Schumacher [mailto:felix.schumac...@internetallee.de]
Sent: Wednesday, February 20, 2019 2:27 AM
To: user@jmeter.apache.org
Subject: Re: The Travis CI build failed


Am 19.02.19 um 21:32 schrieb Felix Schumacher:

Am 19.02.19 um 21:13 schrieb Philippe Mouawad:

Hi Felix,
Are you sure this one is frequent ?

KeepAlive is ,but I don't remember this one occurred recently.

They all look the same to me ;) but I will have a look.

In my mail archives I found at least four test runs that were
affected. I probably deleted quite a few more.

The last that I found in my archive is from 08.09.2018.

On the other hand travis seems to be relatively unaffected by that
test, so I will do a test run of that branch locally.

Hm, it fails locally, too. Now I am letting it run without the changes of 
pr/440.

And that fails, too.

Calling the test plan from the GUI, it reveals that the redirect has changed to 
https://... (it was expectedt to be http://)

Will commit a change before going to sleep.

Felix


Felix


Regards

On Tue, Feb 19, 2019 at 9:10 PM Felix Schumacher <
felix.schumac...@internetallee.de> wrote:


Am 19.02.19 um 07:50 schrieb Sanjay Chaurasia:

Hi team.

I have created a pull request
https://github.com/apache/jmeter/pull/440

.

Earlier, the result of Travis CI build was success but now it is
getting

failed even though I did not make any changes.

Please find the below link for full log.

https://travis-ci.org/apache/jmeter/jobs/494787174

The reported error is a flaky test, that haunts us for quite a long
time now. It has most probably nothing to do with your test case.

Felix



Please let me know to resolve the same. I will be highly grateful
to you.

Thanks and Regards,
Sanjay Chaurasia




- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org



-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org



-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org



Re: JMeter functions do not work in Java application

2019-02-20 Thread glin...@live.com
Double check that:

1. You're using  JMeter 5.0
   (or whatever is the
latest version available at  JMeter Downloads
   page)
2. Your Java application has  ApacheJMeter_functions.jar
  
in its  CLASSPATH   

Assuming above conditions are met you should be able to normally use JMeter
functions in your custom application. 






--
Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html

-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org



JMeter functions do not work in Java application

2019-02-20 Thread Elke

Dear all,

we are running JMeter tests from within a Java application. Test plans 
are created and test runs are initiated programmatically, based on user 
input.


Now we would like to build while loops with complex conditions like that:

${__groovy([not more than x iterations] && [last test failed] && 
[further condition])}


which means that we need a function, e.g. __groovy, to evaluate the 
condition.


The problem is that we could not get the JMeter functions running in 
this setting so far: the condition of the while loop is not evaluated 
correctly, and we run into an infinite loop.


Running exactly the same test plan in the JMeter GUI the loop stops, as 
expected, as soon as the condition evaluates to false.


We supposed that this is probably an issue of missing libraries. 
However, importing ALL JMeter libraries did not solve the problem.



We are grateful for any idea!

Thank you in advance,

Elke Michalsky


--
Trilobyte Software Engineering GmbH
Schliemannstr. 45, 10437 Berlin
Geschäftsführer: Stefan Seide, Sven Gerhardt
Berlin, Amtsgericht Charlottenburg, HRB 103208



how to explain httpclient.reset_state_on_thread_group_iteration= true or false

2019-02-20 Thread 1336230737
hello 
  i saw this sentence:

Since JMeter 5.0, when using default HC4 Implementation, JMeter will reset HTTP 
state (SSL State + Connections) on each thread group iteration. If you don't 
want this behaviour, set httpclient.reset_state_on_thread_group_iteration=false
 . i want to know  set httpclient.reset_state_on_thread_group_iteration=true 
??only works for https??
  because i use jmeter4.0 jmeter3.1 with jmeter5.0 to test ??got the tps 
jmeter3.1= jmeter4.0 , buta huge gap between jmeter 5.0 and them?? so i 
want to know What's wrong with My use and How can I  get the same result with 
4.0 and 5.0