How to troubleshoot problems when using JMeter

Apache JMeter is a Java-based stress testing tool developed by the Apache organization. For stress testing of software, it was originally designed for Web application testing but later extended to other test areas. It can be used to test static and dynamic resources such as static files, Java applets, CGI scripts, Java objects, databases, FTP servers, and so on. JMeter can be used to simulate huge loads on servers, networks, or objects to test their strength and analyze overall performance under different pressure categories.

In addition, JMeter is able to perform functional/regression testing of the application by creating a script with assertions to verify that your program returns the results you expect. For maximum flexibility, JMeter allows you to create assertions using regular expressions.

Apache JMeter can be used to test the performance of static and dynamic resources (files, Servlet,perl scripts, Java objects, databases and queries, FTP servers, and so on). It can be used to simulate heavy loads on servers, networks or objects to test their strength or to analyze the overall performance under different pressure types. You can use it to do graphical analysis of performance or to test your server/scripts/objects in a large concurrent load.

This is a translation of an article on the official website of JMeter.

Click here to access the original jmetertroubleshooting.

Check the log file. This was normally in the launch (i.e. bin) directory, and is called "JMeter.log".

View JMeter log files, usually this log file in the directory you launched JMeter, such as%jmeter_home%in directory, the file name is usually JMeter.log. (The contents of this log file are only the log information related to the JMeter itself, and the execution of the script does not directly related to the situation of script execution, please see the JMeter result file with the extension. jtl--)

Check the JMeter documentation to ensure that the test script have been set up correctly

Review the documentation for the JMeter and confirm that the test script is set up correctly

Check the Jmeterfaq.

View FAQs on the official website of JMeter (FAQ list)

Check the mailing lists to see if anyone else have had the same or a similar problem

View JMeter's user mailing list If someone else has encountered a problem like you or similar (JMeter is a popular open source performance testing tool, and many people are using it for performance testing, so many questions can be found in the mailing list. --the translator's note)

Check bugglgj/bugzilla/' target= ' _blank ' >bugzilla-you might has hit a known bug, and there could be a workround docume nted in bugzilla/' target= ' _blank ' >bugzilla

View the Bugzilla of the official website of JMeter (a well-known bug-tracking management system-the translator's note)-you may have a known bug that has been recorded in the Bugzilla.

Try setting the logging level to DEBUG for some or all of the JMeter packages (details is in the Jmeter.properties file)

Try modifying the log level of JMeter to DEBUG to get more information about the JMeter run to confirm the cause of the problem. (To modify the JMeter log level, search for the log_level in the Jmeter.properties file and modify the appropriate options--the translator's note)

If all the above fail to provide a answer, please read

How to Ask Questions the Smart-before posting a message on the the JMeter User mailing list.

If none of the above can help you solve your problem, please send a message to JMeter's user mailing list-please look at "How smart questions http://www.catb.org/~esr/faqs/smart-questions.html" before sending.

The above content mainly for free translation, while trying to be faithful to the original text, if you find the translation has the original intention of the place, please give me a message, I will immediately modify ^_^

How to troubleshoot problems when using JMeter