limit to number of JMeter properties on command line

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

limit to number of JMeter properties on command line

Greg Phillips
Is there a limit to the number of properties you can pass through to a script using -J?
My script works fine if you pass in three parameters, but produces a segmentation fault if you pass in four.

i.e. this works:
java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3

and this produces a seg. fault:
java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3 -JFOUR=4


Tested on both 3.2 and 4.0.
=============================================================================

This email is intended solely for the recipient and is confidential and not for third party unauthorised distribution. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email or notifying the system manager ([hidden email]).  If you are not the intended recipient you must not disclose, distribute, copy, print or rely on this email.

Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of Hargreaves Lansdown. In addition, staff are not authorised to enter into any contract through email and therefore nothing contained herein should be construed as such. Hargreaves Lansdown makes no warranty as to the accuracy or completeness of any information contained within this email. In particular, Hargreaves Lansdown does not accept responsibility for any changes made to this email after it was sent.

Hargreaves Lansdown Asset Management Limited (Company Registration No 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155) and Hargreaves Lansdown Advisory Services Limited (No 3509545) are authorised and regulated by the Financial Conduct Authority and registered in England and Wales. The registered office for all companies is One College Square South, Anchor Road, Bristol, BS1 5HL. Telephone: 0117 988 9880
Reply | Threaded
Open this post in threaded view
|

RE: limit to number of JMeter properties on command line

Stuart Kenworthy
This is either a Java or shell limitation. I had a similar problem. One way around it is to maintain the list in user.properties or system.properties where your entries would look like

ONE=1
TWO=2
THREE=3

They will still be used the same in the script.

-----Original Message-----
From: Greg Phillips [mailto:[hidden email]]
Sent: 15 February 2018 11:37
To: [hidden email]
Subject: limit to number of JMeter properties on command line

Is there a limit to the number of properties you can pass through to a script using -J?
My script works fine if you pass in three parameters, but produces a segmentation fault if you pass in four.

i.e. this works:
java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3

and this produces a seg. fault:
java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3 -JFOUR=4


Tested on both 3.2 and 4.0.
=============================================================================

This email is intended solely for the recipient and is confidential and not for third party unauthorised distribution. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email or notifying the system manager ([hidden email]).  If you are not the intended recipient you must not disclose, distribute, copy, print or rely on this email.

Any opinions expressed in this document are those of the author and do not necessarily reflect the opinions of Hargreaves Lansdown. In addition, staff are not authorised to enter into any contract through email and therefore nothing contained herein should be construed as such. Hargreaves Lansdown makes no warranty as to the accuracy or completeness of any information contained within this email. In particular, Hargreaves Lansdown does not accept responsibility for any changes made to this email after it was sent.

Hargreaves Lansdown Asset Management Limited (Company Registration No 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155) and Hargreaves Lansdown Advisory Services Limited (No 3509545) are authorised and regulated by the Financial Conduct Authority and registered in England and Wales. The registered office for all companies is One College Square South, Anchor Road, Bristol, BS1 5HL. Telephone: 0117 988 9880

The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: limit to number of JMeter properties on command line

Felix Schumacher
Am 15.02.2018 14:12, schrieb Stuart Kenworthy:
> This is either a Java or shell limitation. I had a similar problem.
> One way around it is to maintain the list in user.properties or
> system.properties where your entries would look like
>
> ONE=1
> TWO=2
> THREE=3
>
> They will still be used the same in the script.

Or you can try to use the --addprop option to use your own properties
file.
(http://jmeter.apache.org/usermanual/get-started.html#options)

Felix

>
> -----Original Message-----
> From: Greg Phillips [mailto:[hidden email]]
> Sent: 15 February 2018 11:37
> To: [hidden email]
> Subject: limit to number of JMeter properties on command line
>
> Is there a limit to the number of properties you can pass through to a
> script using -J?
> My script works fine if you pass in three parameters, but produces a
> segmentation fault if you pass in four.
>
> i.e. this works:
> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>
> and this produces a seg. fault:
> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
> -JFOUR=4
>
>
> Tested on both 3.2 and 4.0.
> =============================================================================
>
> This email is intended solely for the recipient and is confidential
> and not for third party unauthorised distribution. If an addressing or
> transmission error has misdirected this email, please notify the
> author by replying to this email or notifying the system manager
> ([hidden email]).  If you are not the intended recipient you
> must not disclose, distribute, copy, print or rely on this email.
>
> Any opinions expressed in this document are those of the author and do
> not necessarily reflect the opinions of Hargreaves Lansdown. In
> addition, staff are not authorised to enter into any contract through
> email and therefore nothing contained herein should be construed as
> such. Hargreaves Lansdown makes no warranty as to the accuracy or
> completeness of any information contained within this email. In
> particular, Hargreaves Lansdown does not accept responsibility for any
> changes made to this email after it was sent.
>
> Hargreaves Lansdown Asset Management Limited (Company Registration No
> 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155) and
> Hargreaves Lansdown Advisory Services Limited (No 3509545) are
> authorised and regulated by the Financial Conduct Authority and
> registered in England and Wales. The registered office for all
> companies is One College Square South, Anchor Road, Bristol, BS1 5HL.
> Telephone: 0117 988 9880
>
> The information included in this email and any files transmitted with
> it may contain information that is confidential and it must not be
> used by, or its contents or attachments copied or disclosed to,
> persons other than the intended addressee. If you have received this
> email in error, please notify BJSS. In the absence of written
> agreement to the contrary BJSS' relevant standard terms of contract
> for any work to be undertaken will apply. Please carry out virus or
> such other checks as you consider appropriate in respect of this
> email. BJSS does not accept responsibility for any adverse effect upon
> your system or data in relation to this email or any files transmitted
> with it. BJSS Limited, a company registered in England and Wales
> (Company Number 2777575), VAT Registration Number 613295452,
> Registered Office Address, First Floor, Coronet House, Queen Street,
> Leeds, LS1 2TW.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: limit to number of JMeter properties on command line

Stuart Kenworthy
Thanks Felix. I have been trying to use this in the past but find it unreliable, especially when dealing with properties you may want in jmeter.properties or system.properties and don't have write access to the jmeter directory.

I have written a jmeter_conf package which merges default jmeter properties files with custom properties files even if you don't have write access to the jmeter install, something we have come across quite a lot.

https://github.com/stuartjk1606/jmeter_conf

Either way, for large (or small in this case) counts of properties, a *.properties file is the way to go.

-----Original Message-----
From: Felix Schumacher [mailto:[hidden email]]
Sent: 15 February 2018 13:27
To: JMeter Users List <[hidden email]>
Subject: Re: limit to number of JMeter properties on command line

Am 15.02.2018 14:12, schrieb Stuart Kenworthy:
> This is either a Java or shell limitation. I had a similar problem.
> One way around it is to maintain the list in user.properties or
> system.properties where your entries would look like
>
> ONE=1
> TWO=2
> THREE=3
>
> They will still be used the same in the script.

Or you can try to use the --addprop option to use your own properties file.
(http://jmeter.apache.org/usermanual/get-started.html#options)

Felix

>
> -----Original Message-----
> From: Greg Phillips [mailto:[hidden email]]
> Sent: 15 February 2018 11:37
> To: [hidden email]
> Subject: limit to number of JMeter properties on command line
>
> Is there a limit to the number of properties you can pass through to a
> script using -J?
> My script works fine if you pass in three parameters, but produces a
> segmentation fault if you pass in four.
>
> i.e. this works:
> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>
> and this produces a seg. fault:
> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
> -JFOUR=4
>
>
> Tested on both 3.2 and 4.0.
> ======================================================================
> =======
>
> This email is intended solely for the recipient and is confidential
> and not for third party unauthorised distribution. If an addressing or
> transmission error has misdirected this email, please notify the
> author by replying to this email or notifying the system manager
> ([hidden email]).  If you are not the intended recipient you
> must not disclose, distribute, copy, print or rely on this email.
>
> Any opinions expressed in this document are those of the author and do
> not necessarily reflect the opinions of Hargreaves Lansdown. In
> addition, staff are not authorised to enter into any contract through
> email and therefore nothing contained herein should be construed as
> such. Hargreaves Lansdown makes no warranty as to the accuracy or
> completeness of any information contained within this email. In
> particular, Hargreaves Lansdown does not accept responsibility for any
> changes made to this email after it was sent.
>
> Hargreaves Lansdown Asset Management Limited (Company Registration No
> 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155) and
> Hargreaves Lansdown Advisory Services Limited (No 3509545) are
> authorised and regulated by the Financial Conduct Authority and
> registered in England and Wales. The registered office for all
> companies is One College Square South, Anchor Road, Bristol, BS1 5HL.
> Telephone: 0117 988 9880
>
> The information included in this email and any files transmitted with
> it may contain information that is confidential and it must not be
> used by, or its contents or attachments copied or disclosed to,
> persons other than the intended addressee. If you have received this
> email in error, please notify BJSS. In the absence of written
> agreement to the contrary BJSS' relevant standard terms of contract
> for any work to be undertaken will apply. Please carry out virus or
> such other checks as you consider appropriate in respect of this
> email. BJSS does not accept responsibility for any adverse effect upon
> your system or data in relation to this email or any files transmitted
> with it. BJSS Limited, a company registered in England and Wales
> (Company Number 2777575), VAT Registration Number 613295452,
> Registered Office Address, First Floor, Coronet House, Queen Street,
> Leeds, LS1 2TW.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: limit to number of JMeter properties on command line

Felix Schumacher
Am 15.02.2018 um 14:48 schrieb Stuart Kenworthy:
> Thanks Felix. I have been trying to use this in the past but find it unreliable, especially when dealing with properties you may want in jmeter.properties or system.properties and don't have write access to the jmeter directory.
Can you give an example of this behaviour? If it is unreliable it should
be fixed. If it is unexpected (but deterministic) it should be documented.

Felix

>
> I have written a jmeter_conf package which merges default jmeter properties files with custom properties files even if you don't have write access to the jmeter install, something we have come across quite a lot.
>
> https://github.com/stuartjk1606/jmeter_conf
>
> Either way, for large (or small in this case) counts of properties, a *.properties file is the way to go.
>
> -----Original Message-----
> From: Felix Schumacher [mailto:[hidden email]]
> Sent: 15 February 2018 13:27
> To: JMeter Users List <[hidden email]>
> Subject: Re: limit to number of JMeter properties on command line
>
> Am 15.02.2018 14:12, schrieb Stuart Kenworthy:
>> This is either a Java or shell limitation. I had a similar problem.
>> One way around it is to maintain the list in user.properties or
>> system.properties where your entries would look like
>>
>> ONE=1
>> TWO=2
>> THREE=3
>>
>> They will still be used the same in the script.
> Or you can try to use the --addprop option to use your own properties file.
> (http://jmeter.apache.org/usermanual/get-started.html#options)
>
> Felix
>
>> -----Original Message-----
>> From: Greg Phillips [mailto:[hidden email]]
>> Sent: 15 February 2018 11:37
>> To: [hidden email]
>> Subject: limit to number of JMeter properties on command line
>>
>> Is there a limit to the number of properties you can pass through to a
>> script using -J?
>> My script works fine if you pass in three parameters, but produces a
>> segmentation fault if you pass in four.
>>
>> i.e. this works:
>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>>
>> and this produces a seg. fault:
>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>> -JFOUR=4
>>
>>
>> Tested on both 3.2 and 4.0.
>> ======================================================================
>> =======
>>
>> This email is intended solely for the recipient and is confidential
>> and not for third party unauthorised distribution. If an addressing or
>> transmission error has misdirected this email, please notify the
>> author by replying to this email or notifying the system manager
>> ([hidden email]).  If you are not the intended recipient you
>> must not disclose, distribute, copy, print or rely on this email.
>>
>> Any opinions expressed in this document are those of the author and do
>> not necessarily reflect the opinions of Hargreaves Lansdown. In
>> addition, staff are not authorised to enter into any contract through
>> email and therefore nothing contained herein should be construed as
>> such. Hargreaves Lansdown makes no warranty as to the accuracy or
>> completeness of any information contained within this email. In
>> particular, Hargreaves Lansdown does not accept responsibility for any
>> changes made to this email after it was sent.
>>
>> Hargreaves Lansdown Asset Management Limited (Company Registration No
>> 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155) and
>> Hargreaves Lansdown Advisory Services Limited (No 3509545) are
>> authorised and regulated by the Financial Conduct Authority and
>> registered in England and Wales. The registered office for all
>> companies is One College Square South, Anchor Road, Bristol, BS1 5HL.
>> Telephone: 0117 988 9880
>>
>> The information included in this email and any files transmitted with
>> it may contain information that is confidential and it must not be
>> used by, or its contents or attachments copied or disclosed to,
>> persons other than the intended addressee. If you have received this
>> email in error, please notify BJSS. In the absence of written
>> agreement to the contrary BJSS' relevant standard terms of contract
>> for any work to be undertaken will apply. Please carry out virus or
>> such other checks as you consider appropriate in respect of this
>> email. BJSS does not accept responsibility for any adverse effect upon
>> your system or data in relation to this email or any files transmitted
>> with it. BJSS Limited, a company registered in England and Wales
>> (Company Number 2777575), VAT Registration Number 613295452,
>> Registered Office Address, First Floor, Coronet House, Queen Street,
>> Leeds, LS1 2TW.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: limit to number of JMeter properties on command line

glinius@live.com
In reply to this post by Greg Phillips
First of all I cannot reproduce your issue using latest JMeter 4.0 r1823414

<http://www.jmeter-archive.org/file/t340375/Screen_Shot_2018-02-18_at_13.png>

So I would recommend getting used to look into /jmeter.log/ file, in
absolutely majority of cases it contains all the necessary troubleshooting
information. If it doesn't - amend the following line in *log4j2.xml*


> <Root level="info">

to


> <Root level="debug">

and you will get way more information, my expectation is that the root cause
of your problem will also be there. See  Enabling Debug logging
<http://jmeter.apache.org/usermanual/hints_and_tips.html#debug_logging>  
user manual chapter and  How to Configure JMeter Logging
<https://www.blazemeter.com/blog/how-to-configure-jmeter-logging>   article
for more information if needed.







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

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: limit to number of JMeter properties on command line

Stuart Kenworthy
In reply to this post by Felix Schumacher
Beanshell server port, RMI settings and logging patterns are some settings I have looked at setting in additional properties files and being unsuccessful.

I have worked in environments where the base JMeter install is read only and configured by sysadmins so tried to load in additional parameters but only reliable way to get it to use additional settings is to load in a custom jmeter.properties file using -P in command line.

Granted I have not tried it since v3.0 but as I work with a number of different clients with different software policies I have to accommodate 2.13 as well as the later releases in my framework designs.

Thanks

-----Original Message-----
From: Felix Schumacher [mailto:[hidden email]]
Sent: 15 February 2018 19:37
To: [hidden email]
Subject: Re: limit to number of JMeter properties on command line

Am 15.02.2018 um 14:48 schrieb Stuart Kenworthy:
> Thanks Felix. I have been trying to use this in the past but find it unreliable, especially when dealing with properties you may want in jmeter.properties or system.properties and don't have write access to the jmeter directory.
Can you give an example of this behaviour? If it is unreliable it should be fixed. If it is unexpected (but deterministic) it should be documented.

Felix

>
> I have written a jmeter_conf package which merges default jmeter properties files with custom properties files even if you don't have write access to the jmeter install, something we have come across quite a lot.
>
> https://github.com/stuartjk1606/jmeter_conf
>
> Either way, for large (or small in this case) counts of properties, a *.properties file is the way to go.
>
> -----Original Message-----
> From: Felix Schumacher [mailto:[hidden email]]
> Sent: 15 February 2018 13:27
> To: JMeter Users List <[hidden email]>
> Subject: Re: limit to number of JMeter properties on command line
>
> Am 15.02.2018 14:12, schrieb Stuart Kenworthy:
>> This is either a Java or shell limitation. I had a similar problem.
>> One way around it is to maintain the list in user.properties or
>> system.properties where your entries would look like
>>
>> ONE=1
>> TWO=2
>> THREE=3
>>
>> They will still be used the same in the script.
> Or you can try to use the --addprop option to use your own properties file.
> (http://jmeter.apache.org/usermanual/get-started.html#options)
>
> Felix
>
>> -----Original Message-----
>> From: Greg Phillips [mailto:[hidden email]]
>> Sent: 15 February 2018 11:37
>> To: [hidden email]
>> Subject: limit to number of JMeter properties on command line
>>
>> Is there a limit to the number of properties you can pass through to
>> a script using -J?
>> My script works fine if you pass in three parameters, but produces a
>> segmentation fault if you pass in four.
>>
>> i.e. this works:
>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>>
>> and this produces a seg. fault:
>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>> -JFOUR=4
>>
>>
>> Tested on both 3.2 and 4.0.
>> =====================================================================
>> =
>> =======
>>
>> This email is intended solely for the recipient and is confidential
>> and not for third party unauthorised distribution. If an addressing
>> or transmission error has misdirected this email, please notify the
>> author by replying to this email or notifying the system manager
>> ([hidden email]).  If you are not the intended recipient
>> you must not disclose, distribute, copy, print or rely on this email.
>>
>> Any opinions expressed in this document are those of the author and
>> do not necessarily reflect the opinions of Hargreaves Lansdown. In
>> addition, staff are not authorised to enter into any contract through
>> email and therefore nothing contained herein should be construed as
>> such. Hargreaves Lansdown makes no warranty as to the accuracy or
>> completeness of any information contained within this email. In
>> particular, Hargreaves Lansdown does not accept responsibility for
>> any changes made to this email after it was sent.
>>
>> Hargreaves Lansdown Asset Management Limited (Company Registration No
>> 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155) and
>> Hargreaves Lansdown Advisory Services Limited (No 3509545) are
>> authorised and regulated by the Financial Conduct Authority and
>> registered in England and Wales. The registered office for all
>> companies is One College Square South, Anchor Road, Bristol, BS1 5HL.
>> Telephone: 0117 988 9880
>>
>> The information included in this email and any files transmitted with
>> it may contain information that is confidential and it must not be
>> used by, or its contents or attachments copied or disclosed to,
>> persons other than the intended addressee. If you have received this
>> email in error, please notify BJSS. In the absence of written
>> agreement to the contrary BJSS' relevant standard terms of contract
>> for any work to be undertaken will apply. Please carry out virus or
>> such other checks as you consider appropriate in respect of this
>> email. BJSS does not accept responsibility for any adverse effect
>> upon your system or data in relation to this email or any files
>> transmitted with it. BJSS Limited, a company registered in England
>> and Wales (Company Number 2777575), VAT Registration Number
>> 613295452, Registered Office Address, First Floor, Coronet House,
>> Queen Street, Leeds, LS1 2TW.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: limit to number of JMeter properties on command line

Felix Schumacher
Am 19.02.2018 um 10:30 schrieb Stuart Kenworthy:
> Beanshell server port, RMI settings and logging patterns are some settings I have looked at setting in additional properties files and being unsuccessful.
>
> I have worked in environments where the base JMeter install is read only and configured by sysadmins so tried to load in additional parameters but only reliable way to get it to use additional settings is to load in a custom jmeter.properties file using -P in command line.

Do you know, if you mixed different ways of specifying those properties?
Did you use -P on those occasions?

>
> Granted I have not tried it since v3.0 but as I work with a number of different clients with different software policies I have to accommodate 2.13 as well as the later releases in my framework designs.

It would be nice, if you could try again (only on newer installations)
and report any unexpected behaviour.

Felix

>
> Thanks
>
> -----Original Message-----
> From: Felix Schumacher [mailto:[hidden email]]
> Sent: 15 February 2018 19:37
> To: [hidden email]
> Subject: Re: limit to number of JMeter properties on command line
>
> Am 15.02.2018 um 14:48 schrieb Stuart Kenworthy:
>> Thanks Felix. I have been trying to use this in the past but find it unreliable, especially when dealing with properties you may want in jmeter.properties or system.properties and don't have write access to the jmeter directory.
> Can you give an example of this behaviour? If it is unreliable it should be fixed. If it is unexpected (but deterministic) it should be documented.
>
> Felix
>
>> I have written a jmeter_conf package which merges default jmeter properties files with custom properties files even if you don't have write access to the jmeter install, something we have come across quite a lot.
>>
>> https://github.com/stuartjk1606/jmeter_conf
>>
>> Either way, for large (or small in this case) counts of properties, a *.properties file is the way to go.
>>
>> -----Original Message-----
>> From: Felix Schumacher [mailto:[hidden email]]
>> Sent: 15 February 2018 13:27
>> To: JMeter Users List <[hidden email]>
>> Subject: Re: limit to number of JMeter properties on command line
>>
>> Am 15.02.2018 14:12, schrieb Stuart Kenworthy:
>>> This is either a Java or shell limitation. I had a similar problem.
>>> One way around it is to maintain the list in user.properties or
>>> system.properties where your entries would look like
>>>
>>> ONE=1
>>> TWO=2
>>> THREE=3
>>>
>>> They will still be used the same in the script.
>> Or you can try to use the --addprop option to use your own properties file.
>> (http://jmeter.apache.org/usermanual/get-started.html#options)
>>
>> Felix
>>
>>> -----Original Message-----
>>> From: Greg Phillips [mailto:[hidden email]]
>>> Sent: 15 February 2018 11:37
>>> To: [hidden email]
>>> Subject: limit to number of JMeter properties on command line
>>>
>>> Is there a limit to the number of properties you can pass through to
>>> a script using -J?
>>> My script works fine if you pass in three parameters, but produces a
>>> segmentation fault if you pass in four.
>>>
>>> i.e. this works:
>>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>>>
>>> and this produces a seg. fault:
>>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2 -JTHREE=3
>>> -JFOUR=4
>>>
>>>
>>> Tested on both 3.2 and 4.0.
>>> =====================================================================
>>> =
>>> =======
>>>
>>> This email is intended solely for the recipient and is confidential
>>> and not for third party unauthorised distribution. If an addressing
>>> or transmission error has misdirected this email, please notify the
>>> author by replying to this email or notifying the system manager
>>> ([hidden email]).  If you are not the intended recipient
>>> you must not disclose, distribute, copy, print or rely on this email.
>>>
>>> Any opinions expressed in this document are those of the author and
>>> do not necessarily reflect the opinions of Hargreaves Lansdown. In
>>> addition, staff are not authorised to enter into any contract through
>>> email and therefore nothing contained herein should be construed as
>>> such. Hargreaves Lansdown makes no warranty as to the accuracy or
>>> completeness of any information contained within this email. In
>>> particular, Hargreaves Lansdown does not accept responsibility for
>>> any changes made to this email after it was sent.
>>>
>>> Hargreaves Lansdown Asset Management Limited (Company Registration No
>>> 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155) and
>>> Hargreaves Lansdown Advisory Services Limited (No 3509545) are
>>> authorised and regulated by the Financial Conduct Authority and
>>> registered in England and Wales. The registered office for all
>>> companies is One College Square South, Anchor Road, Bristol, BS1 5HL.
>>> Telephone: 0117 988 9880
>>>
>>> The information included in this email and any files transmitted with
>>> it may contain information that is confidential and it must not be
>>> used by, or its contents or attachments copied or disclosed to,
>>> persons other than the intended addressee. If you have received this
>>> email in error, please notify BJSS. In the absence of written
>>> agreement to the contrary BJSS' relevant standard terms of contract
>>> for any work to be undertaken will apply. Please carry out virus or
>>> such other checks as you consider appropriate in respect of this
>>> email. BJSS does not accept responsibility for any adverse effect
>>> upon your system or data in relation to this email or any files
>>> transmitted with it. BJSS Limited, a company registered in England
>>> and Wales (Company Number 2777575), VAT Registration Number
>>> 613295452, Registered Office Address, First Floor, Coronet House,
>>> Queen Street, Leeds, LS1 2TW.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>> The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: limit to number of JMeter properties on command line

Stuart Kenworthy
It was a while ago so a bit hazy but initially, no, I don't recall trying to load in my own main file, just adding new ones either through command line, editing user.properties or --q.

It looks like (both from experimenting and online documentation) jmeter.properties is loaded first, then anything else, even --addprop is read at a lower level. Anything expected in jmeter.properties would then be ignored if present in later files as RMI, networking and such would already be set.

I then moved to using my own properties files using -P. A move between 2.17 and 3 meant I needed a way of running my plans on both versions so maintaining 2 different sets of properties files for a while hence the config util.

I'll have a play around with it when I get chance, but having found a system that works, I'm reluctant to roll it out for another solution, especially as it caters for read only jmeter installs.

-----Original Message-----
From: Felix Schumacher [mailto:[hidden email]]
Sent: 19 February 2018 18:45
To: [hidden email]
Subject: Re: limit to number of JMeter properties on command line

Am 19.02.2018 um 10:30 schrieb Stuart Kenworthy:
> Beanshell server port, RMI settings and logging patterns are some settings I have looked at setting in additional properties files and being unsuccessful.
>
> I have worked in environments where the base JMeter install is read only and configured by sysadmins so tried to load in additional parameters but only reliable way to get it to use additional settings is to load in a custom jmeter.properties file using -P in command line.

Do you know, if you mixed different ways of specifying those properties?
Did you use -P on those occasions?

>
> Granted I have not tried it since v3.0 but as I work with a number of different clients with different software policies I have to accommodate 2.13 as well as the later releases in my framework designs.

It would be nice, if you could try again (only on newer installations) and report any unexpected behaviour.

Felix

>
> Thanks
>
> -----Original Message-----
> From: Felix Schumacher [mailto:[hidden email]]
> Sent: 15 February 2018 19:37
> To: [hidden email]
> Subject: Re: limit to number of JMeter properties on command line
>
> Am 15.02.2018 um 14:48 schrieb Stuart Kenworthy:
>> Thanks Felix. I have been trying to use this in the past but find it unreliable, especially when dealing with properties you may want in jmeter.properties or system.properties and don't have write access to the jmeter directory.
> Can you give an example of this behaviour? If it is unreliable it should be fixed. If it is unexpected (but deterministic) it should be documented.
>
> Felix
>
>> I have written a jmeter_conf package which merges default jmeter properties files with custom properties files even if you don't have write access to the jmeter install, something we have come across quite a lot.
>>
>> https://github.com/stuartjk1606/jmeter_conf
>>
>> Either way, for large (or small in this case) counts of properties, a *.properties file is the way to go.
>>
>> -----Original Message-----
>> From: Felix Schumacher [mailto:[hidden email]]
>> Sent: 15 February 2018 13:27
>> To: JMeter Users List <[hidden email]>
>> Subject: Re: limit to number of JMeter properties on command line
>>
>> Am 15.02.2018 14:12, schrieb Stuart Kenworthy:
>>> This is either a Java or shell limitation. I had a similar problem.
>>> One way around it is to maintain the list in user.properties or
>>> system.properties where your entries would look like
>>>
>>> ONE=1
>>> TWO=2
>>> THREE=3
>>>
>>> They will still be used the same in the script.
>> Or you can try to use the --addprop option to use your own properties file.
>> (http://jmeter.apache.org/usermanual/get-started.html#options)
>>
>> Felix
>>
>>> -----Original Message-----
>>> From: Greg Phillips [mailto:[hidden email]]
>>> Sent: 15 February 2018 11:37
>>> To: [hidden email]
>>> Subject: limit to number of JMeter properties on command line
>>>
>>> Is there a limit to the number of properties you can pass through to
>>> a script using -J?
>>> My script works fine if you pass in three parameters, but produces a
>>> segmentation fault if you pass in four.
>>>
>>> i.e. this works:
>>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2
>>> -JTHREE=3
>>>
>>> and this produces a seg. fault:
>>> java -jar ApacheJMeter.jar -n -t script.jmx -JONE=1 -JTWO=2
>>> -JTHREE=3
>>> -JFOUR=4
>>>
>>>
>>> Tested on both 3.2 and 4.0.
>>> ====================================================================
>>> =
>>> =
>>> =======
>>>
>>> This email is intended solely for the recipient and is confidential
>>> and not for third party unauthorised distribution. If an addressing
>>> or transmission error has misdirected this email, please notify the
>>> author by replying to this email or notifying the system manager
>>> ([hidden email]).  If you are not the intended recipient
>>> you must not disclose, distribute, copy, print or rely on this email.
>>>
>>> Any opinions expressed in this document are those of the author and
>>> do not necessarily reflect the opinions of Hargreaves Lansdown. In
>>> addition, staff are not authorised to enter into any contract
>>> through email and therefore nothing contained herein should be
>>> construed as such. Hargreaves Lansdown makes no warranty as to the
>>> accuracy or completeness of any information contained within this
>>> email. In particular, Hargreaves Lansdown does not accept
>>> responsibility for any changes made to this email after it was sent.
>>>
>>> Hargreaves Lansdown Asset Management Limited (Company Registration
>>> No 1896481), Hargreaves Lansdown Fund Managers Limited (No 2707155)
>>> and Hargreaves Lansdown Advisory Services Limited (No 3509545) are
>>> authorised and regulated by the Financial Conduct Authority and
>>> registered in England and Wales. The registered office for all
>>> companies is One College Square South, Anchor Road, Bristol, BS1 5HL.
>>> Telephone: 0117 988 9880
>>>
>>> The information included in this email and any files transmitted
>>> with it may contain information that is confidential and it must not
>>> be used by, or its contents or attachments copied or disclosed to,
>>> persons other than the intended addressee. If you have received this
>>> email in error, please notify BJSS. In the absence of written
>>> agreement to the contrary BJSS' relevant standard terms of contract
>>> for any work to be undertaken will apply. Please carry out virus or
>>> such other checks as you consider appropriate in respect of this
>>> email. BJSS does not accept responsibility for any adverse effect
>>> upon your system or data in relation to this email or any files
>>> transmitted with it. BJSS Limited, a company registered in England
>>> and Wales (Company Number 2777575), VAT Registration Number
>>> 613295452, Registered Office Address, First Floor, Coronet House,
>>> Queen Street, Leeds, LS1 2TW.
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>> The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
> The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]