Jmeter distributed execution error Solution Summary

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)

  1. The problem is the slave process jmeter listening port is occupied, leading to the port can not be used, given as follows
    Here Insert Picture Description
  2. 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:
    Jmeter distributed execution error Solution Summary
  3. Can be modified into the following
    Jmeter distributed execution error Solution Summary
    two, execution performance measured pressure, a portion of the logs that stuck Master Fixed
  4. Abnormal interface is as follows, during the execution of the task, the results show only a part, will not be successfully completed
    Here Insert Picture Description
  5. 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
    Here Insert Picture Description
  6. 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
    Here Insert Picture Description
  7. 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

  1. Abnormal interface is as follows, during the execution of the task, the results show only a part, will not be successfully completed
    Here Insert Picture Description
    Here Insert Picture Description
  2. 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
    Here Insert Picture Description
    Here Insert Picture Description
    Here Insert Picture Description
  3. Distributed test execution again, master execution log normal display, report generation normal
    Here Insert Picture Description
  4. 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
    Here Insert Picture Description
    Here Insert Picture Description
    four execution performance measured pressure, the execution log suggesting Engine is busy - please try later
  5. The following error interface
    Here Insert Picture Description
  6. 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 Here Insert Picture Description


       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
              Here Insert Picture Description


Micro-channel two-dimensional code number of public attention:

            Here Insert Picture Description


After attention, resources download reply, you can get a variety of shared resources Download

\[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-dkyHNY2D-1569554485737)(https://s1.51cto.com/images/blog/201908/06/2e62f8806e1dc1c391c4332ac7fd70b1.png?x-oss-process=image/watermark,size_16,text_QDUxQ1RP5Y2a5a6i,color_FFFFFF,t_100,g_se,x_10,y_10,shadow_90,type_ZmFuZ3poZW5naGVpdGk=)\]

Guess you like

Origin blog.51cto.com/6183574/2454007