Problem set encountered by Jmeter
Problem 1: The startup process failed and an error was reported.
Reason: The process of copying the Jmeter installation package did not copy all the files, resulting in the loss of lib files.
Solution: Restart jmeter after copying all the files.
Question 2: The following exception was thrown when starting jmeter-server.bat:
Server failed to start: java.rmi.server.ExportException: Listen failed on port:
Cause of the problem: The communication between the Jmeter control machine and the load machine is RMI Complete, so the server-related rmi configuration needs to be adjusted: the meaning of the configuration is: Set this if you don't want to use SSL for RMI
Solution:
Open the file named jmeter.properties and find server.rmi.ssl.disable= Change false to true, remove the # in front, save the configuration adjustment, and restart jmeter-server.bat to return to normal.
Question 3: The working principle of
Jmeter Jmeter is a proxy between Browser and Server, which can obtain the response between Browser and Server, and simulate the concurrency scenario of real business through threads.
Jmeter creates a thread group to generate load on the server . Jmeter uses Multi-threaded simulation of user requests, through the establishment of thread groups, setting the running scene, running Sample to generate load on the Server, and realizing real business concurrency scenarios and configurations through logic controllers and other components (fixed timers, throughput controllers) The component sets variables and data, judges the verification results through assertions, and collects and displays the test results through the listener component
Question 4: Test a single performance interface? It is still a process
interface. A preliminary understanding of the operation of the interface through a single performance interface, but the final performance test is to cover and test the corresponding interface in a process and business-meaning process.