im performancetesting a site with Jmeter that is on an internal environment. However we also have a company proxy which i have configured in the HTTP default request manager in Jmeter.
Now everything works fine, however i keep seeing these WARNINGS in the jmeter.log when im tailing at runtime.
Everytime a thread starts up i see:
2014/02/07 15:35:46 WARN - org.apache.http.client.protocol.RequestProxyAuthentication: NEGOTIATE authentication error: Invalid name provided (Mechanism level: Could not load configuration file C:\WINDOWS\krb5.ini (Het systeem kan het opgegeven bestand niet vinden))
2014/02/07 15:35:48 INFO - jmeter.threads.JMeterThread: Thread started: Mythread 1-4
Does anyone know what this means, and if it is going to cause any problems. Ive tried setting the proxy credentials in like every possible place but it doesnt seem to matter.
Regards,
Johan
You can ignore these messages unless you are testing application which uses Kerberos authentication. If you want it to go away - read below for explanation of what's happening and how to get rid of it.
The warning is for missing Kerberos configuration file in the default location. If you need to test application which assumes Kerberos login, you need to properly configure krb5.conf and jaas.conf files in /bin folder of your JMeter installation. If you're changing application module name in jaas.conf make sure that the same value is present in jmeter.properties or user.properties file as kerberos_jaas_application property. You can also specify the property during JMeter startup as -J parameter, i.e.
jmeter -Jkerberos_jaas_application=testapp -n -t myscript.jmx -l myscript.jtl
and make sure that following two system properties are set:
-Djava.security.krb5.conf=krb5.conf
-Djava.security.auth.login.config=jaas.conf
the paths given are relative to JMeter home folder, you might want to use full paths. See Apache JMeter Properties Customization Guide for more details on how to play with JMeter properties.
Also make sure that you set "Implementation" dropdown to HTTPClient4 in HTTP Request Defaults (or for each HTTP Sampler)
Hope it makes sense
Related
I have applied all the instructions to execute the distributed Testing for JMeter.
But When I run as "Remote Start-XXX.XXX.XXX.XXX"
Then I am getting "Exception creating connection: XXX.XXX.XXX.XXX; nested exception is: java.io.IOException: java.security.UnrecoverableKeyException: Cannot recover key".
Can anyone help me Why I am getting that exception?
Reference that I used: LINK
This is how I solve the same problem as yours. Have a try, hope this can help:
when answering the question What is your first and last name?, you'll have to reply with rmi which is a corresponding value with server.rmi.ssl.keystore.alias in jmeter.propertise. Remember do NOT enter any custom value if u have not changed the server.rmi.ssl.keystore.alias in jmeter.propertise when u are trying to create a keystore.
Given you use JMeter 4.0 additionally you need to follow steps from Setting Up SSL User Manual Chapter
Alternatively if you don't want secure RMI communication between master and slave(s) you can add the next line to user.properties file
server.rmi.ssl.disable=true
or pass it via -J command-line argument like:
jmeter -Jserver.rmi.ssl.disable=true
The change has to be done on all engines (master and all the slaves)
References:
Remote hosts and RMI configuration
Configuring JMeter
In JMeter 4.0 you need to generate a keystore that will be used in distributed testing.
Follow this tutorial instead:
http://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.html
Pay particular attention to:
https://jmeter.apache.org/usermanual/remote-test.html#setup_ssl
I am trying to do a LDAP mod operation through Jmeter. Expected behavior - Jmeter would hit server A which in turn would hit server B. Actual modification operation would happen at server B. Server B would complete the operation and give response to server A which in turn would respond to Jmeter.
Now the issue is, Jmeter is always getting the "Referral" response message. However, manually we are able to change the password after hitting server A from different remote server.
Could you someone please suggest how to overcome this?
I am assuming this has been resolved. Just in case you are still wondering, #Rohan , my understanding is that you run jmeter on the command line:
$ jmeter -Jjava.naming.referral=true -n -t testplan.jmx -l log.jtl
JMeter won't have specific behaviour of its own. You will need to tell it to follow referrals by setting java.naming.referral property appropriately in the jndi.properties mechanism defined in the documentation for the JNDI LDAP provider, which you should already have in place for your application if you expect it to behave that way.
I'm using jmeter 3.2, I want run a SMTP Sampler in Jmeter where I have done the necessary configuration by adding the javamail file in the lib folder of Jmeter and adding necessary credentials in the mail setting, though when executed I am getting an error of IOException.
Am I missing any step?
There was a change in SMTP Sampler in jmeter 3.2 which created several bugs.
You open a bug to jmeter with a sample if it's a different scenario.
If you can downgrade to Jmeter 3.1 if it can work.
EDIT
You can download a fix to the issue in jmeter-3.3
If you are trying to send a file as an attachment you have 2 options:
If you are using relative path (just filename) make sure you put the file into JMeter's "bin" folder. So JMeter could find it. Check out jmeter.log file to know where JMeter is expecting the file to be.
Use full path (like c:\somefolder\someotherfolder\somefile.eml)
In case if you still experience the problem update your question with your email server configuration and jmeter.log file contents. In the meantime check out Load Testing Your Email Server: How to Send and Receive E-mails with JMeter article
I have a working script to login and get to one website on the webserver, what I need is how to get to the other 10 plus servers with Jmeter all at once to do a nice stress test on the websites and its interfaces.
Any help is greatly appreciated
I think that you need to use DNS Cache Manager available since JMeter 2.12
DNS Cache Manager allows each JMeter thread to resolve underlying IP address of the request endpoint on its own.
See The DNS Cache Manager: The Right Way To Test Load Balanced Apps guide for detailed explanation of background and configuration details.
This is pretty trivial using the CSV Data Set Config.
Let's assume you are using normal HTTP Request samplers and that these are already set up with a server and path. Let's say it is the server you want to change for each thread. Then you need to:
Create a text file with a different server you want to test on each line.
Add a CSV Data Config element to the top level.
Configure the CSV Data Config to use your text file and set the variable name of server.
In your samplers change the server name to ${server}.
You can use the same method to change the path and other details.
I have a prepared a jmx file using jmeter & ran that test case on blazemeter to test load on my server. After the test is done, I can see that one of my services are failing. Though not all the time, but some times. And in the error tab on blazemeter, i can see that is is giving
Non HTTP response message: The target server failed to respond
I am not sure, that is my server failing to handle the load, or is it something else. In My settings, thread is 50. Can any one please help me that, is this because of server is failing to handle to load. Thanks in advance.
It looks like that you're facing the problem described in Connection Reset since JMeter 2.10 ? Wiki article.
If you upgraded recently to JMeter 2.10 or 2.11, you may have noticed increased errors of this type:
Socket closed
Non HTTP response code: org.apache.http.NoHttpResponseException (the target server failed to respond)
So
Change "Implementation" of your HTTP Requests to HTTPClient4
Add the next 2 lines to user.properties file (usually lives under /bin folder of your JMeter installation)
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
In hc.parameters file (also lives under JMeter's /bin folder) uncomment the following line:
http.connection.stalecheck$Boolean=true
For more information on different JMeter properties and ways of setting and altering them refer to Apache JMeter Properties Customization Guide
Encountered the same issue and fixed it by unchecking the "Use KeepAlive" option for HTTP requests. Please refer to the screenshot. I guess, the root cause was related to the connection being closed and the JMeter client trying to use the same connection.
Had similar problem for jmeter 2.13 DmitriT solution got me pointed in right direction, but in my case the java or HttpClient3.1 worked, 4.0 did not.
I have done everything.
ange "Implementation" of your HTTP Requests to HTTPClient4
Add the next 2 lines to user.properties file (usually lives under /bin folder of your JMeter installation)
httpclient4.retrycount=1
hc.parameters.file=hc.parameters
In hc.parameters file (also lives under JMeter's /bin folder) uncomment the following line:
http.connection.stalecheck$Boolean=true
BUT STILL FACING THIS ISSUE in apache jmeter 5.1
In my case it was the header for the call I was doing that was causing the issue.
It was:
Content-Type:application/json;charset=UTF-8
Set it to:
Content-Type:application/json