JMeter those pits that have been trampled in distributed testing.

Http://www.cnblogs.com/Fine-Chan/p/6233823.html

Recently, due to the needs of the project, the performance testing of the relevant content, and finally selected JMeter this lightweight open source tool.   Since the use of JMeter GUI mode for scripting, to the test execution phase of the tool itself on the excessive consumption of resources to the performance test brings a bottleneck, the general thread added to 100 or so will be the tool itself can not support the problem, a wide understanding of the solution, found that distributed deployment testing machine is still the preferred solution. about how to configure the JMeter distributed Deployment test machine Many of the blogs have been described in detail, here will not repeat, you can refer to the Zerg blog: http://www.cnblogs.com/fnng/archive/2012/12/29/2839420. HTML now simply records the pits that have been trampled during the deployment of the distributed test machine.five-star pit: Remote boot test, response data is empty. After the controller runs the JMeter script, the GUI has no performance data to return. The agent's JMeter server displays the connection immediately after the end. Seemingly executing the response data is empty.The reasons for the above situation and solutions:1, JMeter script and test data (if any) both host and slave on both sides to be stored.   and the controller in the JMeter script, test data storage path and agent in the JMeter script, test data storage path consistent. 2, on the basis of Reason 1, controller's test data address to use absolute path, Agent test data absolute path or relative path can be.Workaround: After the file address has been modified, the operation is successful. (Run is the log that you hit) (note: Also because the path is consistent, I have no way to mix windows and Mac computers as a distributed test machine, this is exclusively's Windows system) four-star pit: The agent's VM or shared drive will interfere with remote connectionsAgent If you install a VM or set a disk share permissions, the controller in the configuration of the agent in addition to the IP address, virtual machine IP or shared disk IP will also appear in the remote connection to choose the list, connect the times wrong.workaround: Shut down or uninstall the virtual machine and revoke the drive letter sharingSamsung Pit: JMeter run times memory overflow outfmenmory error. The problem blog has a lot of peers have given the solution,For example, modify the default memory size of Jmeter.bat。 Refer to the Crazy Tiger blog: http://www.cnblogs.com/yang-hao/p/5319720.htmlTwo star pit: The remote connection is affected because the firewall is not shutting down or if the controller and agent are not on the same network segment. Workaround: Close the agent's firewall. Contrller and agent in the same network segment, for example, I chose the same wifi, configure the same DNS and other methods to solve. At this point, jmeter distributed testing is barely into the right track, will step on the pit to make a memo.   Thank the team for their efforts, but also hope to work with you to learn, share, progress. Author: Snail in Chengdu Source: http://www.cnblogs.com/Fine-Chan//This article copyright belongs to the author and the blog Park is shared, welcome reprint, but without the author's consent must retain this paragraph, and in the article page obvious location to give the original text connection, otherwise retain the legal responsibility Right