I want to perform distributed performance testing in JMeter, I am unable to create the rmi_keystore.jks as error is showing in command prompt, I have tried in many different way but unable to create, If I run the Jmeter and go to run option and select the IP then Error is showing as I was unable to create the keystore file.
I am stuck at the beginning.
Please refer screenshot of Error for reference.
Ensure you install a JDK 8 and that you have in Windows path :
<full path to jdk_home>/bin
Or edit the create-rmi-keystore.bat and add the full path before keytool:
"C:\Program Files\Java\jdk-10.0.2\bin\keytool"
Run the command create-rmi-keystore.bat once and then copy the file on all machines.
The error you're getting is due to missing keytool.exe utility in your operating system path, most probably your Java installation is partially broken.
The question is: do you really need to create this rmi_keystore.jks file? If you're afraid that your very important test metrics like response time or latency can be stolen by a malefactor - make sure to add the "bin" folder of your JRE or JDK to PATH like:
set PATH=c:\java\bin;%PATH%
jmeter.bat
If your environment is safe enough you can turn off encryption of the traffic between JMeter master and slaves by adding the next line to user.properties file (it has to be done on all nodes)
server.rmi.ssl.disable=true
or alternatively pass the above property via -J command-line argument like:
jmeter.bat -Jserver.rmi.ssl.disable=true
As a bonus you will get slightly increased maximum number of virtual users/throughput as encryption/decryption of data is a quite CPU-intensive process
The answer is inspired in part by JMeter Distributed Testing with Docker article
After adding the path of keytool it works
I have added the following path in create-rmi-keystore.bat file
"C:\Program Files\Java\jdk-10.0.2\bin\keytool" -genkey -keyalg RSA -alias rmi -keystore rmi_keystore.jks -storepass changeit -validity 7 -keysize 2048 %*
Related
When I launch JMeter and start a recording in the "HTTP(S) Test Script Recorder" a window pops-up indicating that a Root CA certificate has been generated in the JMeter bin directory, but when I go to the bin directory there isn't any certificate there.
I am using JMeter 5.4.1 on Windows 10.
Based on this, I tried launching JMeter with administrator permissions and checked the permissions of the bin directory but still no certificate was generated.
As suggested here, I also tried to delete the files ApacheJMeterTemporaryRootCA.crt, ApacheJMeterTemporaryRootCA.usr and proxyserver.jks from the bin directory. Afterwards, I launched JMeter again and started the recorder but still no certificate was generated.
I also tried using a different version of JMeter and downloaded version 5.4.3, but the certificate was still not generated.
[EDIT]
According to Dmitri T's suggestion, the jmeter log can be viewed here.
We cannot help without seeing your jmeter.log file, better with debug logging enabled.
Look for the following line:
ProxyControl: Created keystore in
it will contain the path where the certificates are created. If not the log file will display the error.
You may also find JMeter Chrome Extension easier to use, in this case you won't have to worry about proxies and certificates.
It seems I managed to find a solution to my problem. The value I had on the system and user variable _JAVA_OPTIONS was causing the failure. I deleted those variables and the certificate was generated again.
Im working with Jmeter, trying to running it as a proxy, but when I start recording, I got this alert. I tried setting user.properties, but i can’t find a solution. Please, so grateful if you help me!
In order to be able to record HTTPS traffic JMeter generates special MITM certificate which needs to be installed in the browser
In order to be able to generate the certificate JMeter needs keytool command which normally lives in "bin" folder of JDK or JRE
So make sure to add the "bin" folder of your Java installation to your operating system PATH and it should resolve your issue.
Example command on Windows:
setx PATH=c:\java\bin;%PATH% && jmeter.bat
Example command on Unix and derivatives:
PATH=/opt/java/bin:$PATH && ./jmeter.sh
Replace c:\java or /opt/java with the real path to your JDK or JRE installation.
You should get something like:
if you launch JMeter from the same terminal window you will be able to start the HTTP(S) Test Script Recorder without any issues
Also be aware that there is an easier way of recording a JMeter test: JMeter Chrome Extension, in this case you won't have to worry about proxies and SSL certificates
I am new to Jmeter 5.1.1 however I am in the process of setting up a remote testing with it.
One step I'm having trouble with is running 'create-rmi-keystore.bat' when I double click it nothing happens. I have tried to open it using the command line and get the following message.
'keytool' is not recognized as an internal or external command,
operable program or batch file.
"Copy the generated rmi_keystore.jks to jmeter/bin folder or reference it in property 'server.rmi.ssl.keystore.file'"
I don't seem to have a rmi-keystore.jks .
Has anyone managed to solve this issue?
You don't have keytool utility in your Windows PATH, all you need to do is to ensure that it's there.
Solution using Windows Command Prompt would be:
set PATH="path\to\bin\folder\of\your\JDK\or\JRE\installation";%PATH%
In general if you don't need the secure RMI communication between JMeter master and slave machines (and 99% of people don't need this as it doesn't add any value and only creates overhead in terms of CPU and RAM) you can just disable this functionality by adding the next line to user.properties file:
server.rmi.ssl.disable=true
References:
Remote hosts and RMI configuration
Apache JMeter Properties Customization Guide
If you do this on JMeter master and all the slaves you will not have to worry about the RMI keystore, but I would still recommend having the keytool in the PATH otherwise you will not be able to use HTTP(S) Test Script Recorder for recording secure traffic.
I have Set up everything, running Jmeter-Server.bat file in slave system, added IP in Jmeter.properties. It was running before one month properly, but when I am trying to run, Its showing me the Error.
Most probably there is a mismatch between certificates in master and slave(s) or 7 days had passed since the last keystore creation so the certificates are exired now.
Either follow steps from Setting up SSL one more time and make sure to use exactly the same rmi_keystore.jks file on master and all the slaves or define the following property:
server.rmi.ssl.disable=true
This can be done either by adding the above line to user.properties file or alternatively you can provide it using -J command-line argument like:
jmeter -Jserver.rmi.ssl.disable=true ..... - on master
jmeter-server -Jserver.rmi.ssl.disable=true ..... - on slaves
More information:
Remote hosts and RMI configuration
Apache JMeter Properties Customization Guide
Overriding Properties Via The Command Line
I am following JMeter User guide to start recording my first test plan. When I click the Start button in HTTP Test Script Recorder, I got this error:
Could not create script recorder – see log for details >> keytool error:java.io.FileNotFoundException: proxyserver.jks (Access is denied)
How could I fix this error? Thanks in advance.
Background: JMeter creates a self-signed SSL certificate in order to be able to decrypt and record HTTPS requests, this proxyserver.jks is a Java Keystore which is being generated by JMeter in its "bin" folder when you start HTTP(S) Test Script Recorder proxy
Explanation: The error you are getting most probably indicates that you don't have permissions to write anything into the "bin" folder of your JMeter installation
Workarounds:
You can try launching JMeter with elevated rights (run as administrator or superuser or whoever having write access to JMeter's "bin" folder
You can change the location where JMeter tries to generate this proxyserver.jks file by adding the next line to user.properties file:
proxy.cert.directory=/path/to/folder/where/you/have/write/access
JMeter restart will be required to pick the property up.
Another option is passing the property value via -J command-line argument like
jmeter -Jproxy.cert.directory=/path/to/folder/where/you/have/write/access -n -t ....
Check out Apache JMeter Properties Customization Guide for more information regarding JMeter properties and ways of setting and overriding them
One workaround that worked for me was to start JMeter.bat from bin folder from cmd which was "run as administrator". After this, the error was gone.