Using JMeter distributed test execution, often encounter a variety of error, this paper summarized several issues at work often encountered
as windows 1, article master end, slave end for the Linux
2, regardless of master and slave in windows or linux, we must first ensure that the network is through, telnet ip port on the line
3, suitable for high-volume call jmeter platform for performance testing troubleshooting, port occupation, slave closes unexpectedly, resulting in zombie master terminal
First, the implementation of performance pressure measurement, execution log prompted Failed to create UDP port (UDP port creation failed)
- The problem is the slave process jmeter listening port is occupied, leading to the port can not be used, given as follows
- Solution, only need to modify the master machine jmeter.property file, the configuration file in the bin directory jmeter, the default configuration is only open 10 ports to monitor the scope of use, only need to be modified to:
- Can be modified into the following
two, execution performance measured pressure, a portion of the logs that stuck Master Fixed - Abnormal interface is as follows, during the execution of the task, the results show only a part, will not be successfully completed
- The problem, probably the largest slave process was unexpectedly shut down, such as not enough memory, resulting in abnormal shutdown, master slave monitor is less than the news, it has been hung lead
- First, the slave machine by netstat -anp | grep 1100, see the slave occupied port is normal, the following figure represents the port is not occupied, slave process has closed, resulting master has been stuck not moving, you need to restart the slave, again pressure test, to see if the slave machine jmeter-server.log logs have reported running out of memory, you need to modify the default maximum memory
- When the problem occurs, the master process will not be closed until consumes system resources, windows can be closed directly execute interface, linux page you need to kill off the master execution process
Third, the execution performance measured pressure, Master log does not return any result of execution, slave there execution log
- Abnormal interface is as follows, during the execution of the task, the results show only a part, will not be successfully completed
- The problem, first check the slave machine jmeter-server.log log in the bin directory, the logs may be prompted to connect 169.254.217.204 exception Check your phone ip, ip was found that a virtual network card, just need to disable it network connection to
- Distributed test execution again, master execution log normal display, report generation normal
- First, to ensure that the master machine and the slave machines is through a network, needs to be performed in the master telnet 10.16.69.174 1100, ip IP machine is slave, slave port is port side arranged, if the normal access command interface, and a slave terminal connected demonstrated is through
four execution performance measured pressure, the execution log suggesting Engine is busy - please try later - The following error interface
-
The problem is that slave is occupied not been released, may not be properly closed when the master execution, resulting in slave has been occupied only need to close the slave service, you can restart the operation command is as follows, first of all netstat -anp | grep 1100, check out the slave process id, then you can kill -9 id
If the article helpful, I welcome attention to public numbers, the public numbers this article synchronized platform, facilitate access, I will continue to introduce articles related to testing, testing technology to share with you, each one original article is carefully written to you eliminate plagiarism copy
QQ technical exchange group: the group please enter this information 51CTO
Micro-channel two-dimensional code number of public attention:
After attention, resources download reply, you can get a variety of shared resources Download