The same script works in jmeter 3.1 but not in jmeter 3.2, why?
Can someone answer that?
EDIT 1:
Open bug for jmeter.
There was a change in SMTP Sampler in jmeter 3.2
Which wasn't tested. I suggest you open a bug to jmeter with a sample.
If you can't post bug I can post it for you if you give sample jmx that doesn't work.
If you can downgrade to Jmeter 3.1 it can work.
I understand this is a fairly big change with no tests but I thought
I'd submit anyway in the hope that someone had some good SMTP tests or
someone was willing to review or even just apply a subset of the
changes.
There's also existing bug reported on SMTP Smapler in Jmeter 3.2.
EDIT
You can download a fix to the issue in jmeter-3.3
I got it to work in Jmeter 3.2.
I got the report stored in a file and gave the path to that file "Attach file(s)" section and its sending email successfully.
Related
I am trying to execute a .jmx script in the GitHub. The login page requires a OTP, which I am generating using org.jboss.aerogear. However, it seems when I am executing the script in GitHub the script is not generating this OTP and throwing 406 (Not Acceptable). Can anyone please guide me on this issue please.
This is running perfectly in JMeter but getting error in GitHub.
Do I need to add this specific driver and how?
Whenever you face any "error" first of all take a look at jmeter.log file, normally it contains the reason or at least a clue so you can figure out or guess the error cause. If it doesn't - increase JMeter logging verbosity for the test elements you're using.
Most probably you need to add the .jar file which provides this Totp class (along with dependencies, if any) to JMeter Classpath to JMeter installation in "Github" (whatever it means) and the error will go away
The question was already posted by Chintamani here however it has not been answered.
I'm trying to get the details of my error through the generated dashboard report by JMeter but it's not detailed out in the report. It just indicates that an assertion failed.
Rather than just indicating Assertion Failed in the Type of error. I would want for the report to display the custom response assertion error message that I indicated in the response assertion. I hope someone can help. Thanks!
EDITS:
I have replicated the issue here. It still indicating assertion failed. Not sure what I'm missing here. Also, I am using the updated JMeter version 5.2.1.
This is my result save configuration on my simple data writer.
I cannot reproduce your issue using latest stable JMeter version 5.2.1:
According to 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure you should be using the latest version of JMeter so consider upgrading to JMeter 5.2.1 (or whatever is the latest stable JMeter version which is available at JMeter Downloads page) and the issue will go away.
If you're using the latest version already it might be the case you're looking into "old" results, re-run your test providing -f command-line argument so JMeter would overwrite the previous .jtl results file and the dashboard folder with the new results
Check for properties jmeter.save.saveservice.assertion_results_failure_message=false
This should be equal to true or just remove/comment before running again.
I am using Jmeter 3.3 for executing performance script. Currently Java got upgraded in server from 1.7 to 1.8. Now while executing script on submitting SSO stub page for doing SSL handshake where there is redirection from one end point URL to another exists, its taking more than 60secs to redirect, whereas manually it hardly takes15-20 secs. Same script took hardly 10secs before java upgrade. Any idea how to resolve this Jmeter issue
This might be due to JEP-115 which adds GCM algorithm which is on one hand secure and on another is quite slow or other security enhancements
If it impacts your tests you can disable the algorithm by taking the next steps:
Create java.security file in "bin" folder of your JMeter installation
Add the next line to it:
jdk.tls.disabledAlgorithms=SSLv3,GCM
Then add the next line to system.properties file (lives in "bin" folder of your JMeter installation)
java.security.properties=java.security
Also consider upgrading to JMeter 4.0 as you should be always using the latest JMeter version according to JMeter Best Practices
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
We experienced a strange issue sporadically, that the jmeter test result xml is malformed, for example two lines are swapped by each other, which makes the xml invalid at all. We execute jmeter test cases through command line. Anyone has such experience? Thanks.
Best Regards,
There are no known bug related to this.
If you confirm that without any 3rd party plugin you face this issue, then please report a bug to jmeter:
http://jmeter.apache.org/issues.html
They will be happy to fix it ASAP.
Provide a simple test plan, how you are exporting XML (which listener or is it through -l ?) , user.properties and jmeter.properties and jmeter.log.