Distributed concurrency testing and Web API interface testing using JMETER3.0 combat

Brief introduction:

This document is based on Apche JMeter-3.0 as an example, through the online learning materials and official documentation of the instruction manual after learning, the project operation practice, the test process is documented to provide for everyone to learn.

The main content of this blog is to configure JMeter test parameters, carry out concurrent testing, distributed testing and collection of server-side performance parameters and how to test the Web API interface methods.

This blog post takes a working project as a test case for concurrent testing. If there is an error, please point out.

1. Recording Web performance test scripts using Badboy 1.1 using the Badboy tool for recording Web performance test scripts

(1) Start Badboy. When you first start Badboy, the Record button is selected by default in the red dots.

(2) Enter the test URL in the Badboy tool address bar and press ENTER. The Badboy tool will use the built-in browser to access the corresponding URL.

(3) To complete the actions required to log in on the page that the Badboy tool opens, you can see the test script generated by the recording in the script box in the upper-left corner.

1.2 Export badboy test script (1) After you complete the script recording in Badboy, you can export the test script to the JMX format for subsequent jmeter use.

2. Create a Web Test Plan 2.1 import Badboy recorded test script (1) Open Jmeter->file->open, select Save Badboy recorded test script, click the Open button.

2.2 Configuration properties and parameters (1) After the HTTP header manager is selected, depending on the requirements of the test, you can modify the information in the header manager for headers Stored in this case, adding content-type key-value pairs.

Set the HTTP header information

Setting configuration information for HTTP request

Set the configuration information for the HTTP request and set the parameter content for the send

2.3 parameterization

(1) Function Assistant can be opened with ctrl-f, through the function Assistant to find the _csvrrad method, enter the path of the parameter file, the CSV file column number is starting from 0, the first column 0, the second column 1, the third column 2, and so on.

Then clicking the "Generate" button will automatically generate the parametric function we need.

Open a parameterized window

setting parameterized files and getting parameterized columns

(2) Copy the generated parametric function, open the landing Request page, in the right of the parameterization to find the field we want to parameterize, here the user name and password to do the parameterization, the first column is the user name, the column number is 0;

The second column is the password, the column number is 1, and the corresponding parameterized field column number in the function can be changed.

2.4 Regular Expressions (1) because the project is designed to prevent CSRF attacks, a token is added to the page, which can be found on the page, and if the current page is to get to the string, the HTTP request must be sent on the previous page.

Extracts the string from the response of the request, using the method of regular expression.

(2) Regular Expressions extract data

To create a regular expression

(3) Fill in the regular expression information

Reference Address: http://book.51cto.com/art/201204/327425.htm

2.5 Adding test results listeners (1) Adding test results listeners for test steps (View Results Tree)

2.6 Setting up Remote server monitoring (1) When doing load testing, we should always be concerned about the Cpu,mem of the server ... Use, but JMeter itself does not collect the information, and this time the perfmon was born.

He is used to collect various performance indicators of the compressed server, for example: CPU, Memory, Swap, Disks I/O and Networks I/o ...

Environment construction
: http://jmeter-plugins.org/downloads/all/
Unzip the ZIP package and place the Jmeterplugins-standard.jar under the jmeter/lib/ext of the JMeter client
Start JMeter and add listener when you see Perfmon Metrics Collectors

(2) Configuring the monitored server
: Http://jmeter-plugins.org/downloads/file/ServerAgent-2.2.1.zip
Unzip the zip package, put the ServerAgent-2.2.1 under the monitored server, must start the Startagent.bat, and the test can not close the window, the successful start, the default port is 4444

(3) Adding monitored server metrics

3. Run the test Plan 3.1. Set the number of concurrent users

Depending on the requirements of the test, you can set the number and time of concurrent users and the number of cycles.

3.2. Run the test plan

Run a test plan

View reports that monitor remote servers

After the run, review the Cpu,io, memory, and network statistics reports that monitor the remote server.

4. Attachment Configuration 4.1. Configure information metrics to collect monitored servers by default, the frequency of collecting the server's performance metrics data is 1 seconds, and if the collection frequency is too high, you can set the phone time. In the JMeter directory: \apache-jmeter\bin\ found the jmeter.properties file,

For editing, if no JmeterPlugin.perfmon.interval is found in the file, add it to the end of the document.

For example, settings are collected every 5 seconds: jmeterplugin.perfmon.interval=5000

Other option settings:
? Jmeterplugin.perfmon.interval-metrics collection interval in milliseconds
? Jmeterplugin.perfmon.useudp-true/false, enabling UDP connection try after failed TCP connection attempt
? Jmeterplugin.perfmon.label.usehostname-true/false, enable using "short" hostnames, the default pattern is ([\w\-]+) \. *
? Jmeterplugin.perfmon.label.usehostname.pattern-string (escaped), regular expression to extract hostname (first group is Matched)
? e.g. Default pattern would
? Be:jmeterplugin.perfmon.label.usehostname.pattern= ([\w\-]+) \. *
? e.g. Pattern for EC2 us-east/west subdomain
? Matching:jmeterplugin.perfmon.label.usehostname.pattern= ([\w\-]+\.us-(East|west)-[0-9]). *
? Forceperfmonfile-true/false, enabling it makes JMeter to write JTL file with Perfmon metrics in the current directory
For more configuration settings, please refer to: http://jmeter-plugins.org/wiki/PerfMon/

4.2. Configure Sample Batches

(1) After the distributed test, in the control side, when viewing the View Results tree, after clicking the tab response data, the returned response data is not displayed. At this point, you need a directory in JMeter

Next: \apache-jmeter\bin\ Find the Jmeter.properties file, edit it, find the Mode=standard, and save the #.

Mode=standard configuration found in jmeter.properties file Remote batching Config palette

Remove the # number in front of the mode=standard so that the view result tree in the distributed test console can see the data in response.
Additional parameter configuration:
The listeners in the test plan return their results to the JMeter client, and the JMeter client writes these results to the specified file by default, and the sample results are sent back to the JMeter client as soon as it is generated.

This can create a lot of pressure on the network and JMeter clients. Users can change the default action by setting some properties.

Pattern (mode) (sample result send mode) is standard by default.

Standard : sent immediately after the sample results have been generated.
Hold : saves the sampled results in an array until the test is finished. This may consume a large amount of memory on the remote server.
Batch: sends the saved sample results when the counter or time exceeds the threshold value.
Statistical: when the counter or time exceeds the threshold, the sampled results are sent as a summary, and the sampling results are summarized in the thread group name and sample label.

The accumulated data fields include: elapsed time, latency, Bytes, sample count, error count, and other data fields will be discarded.

stripped: The response data for the successful sample is removed.
Strippedbatch: The response data for the successful sample is removed and sent in batches.
Custom Implementation: sets the mode parameter to the class name of the tester's custom sample sender. The class must implement Interface Samplesender, and the constructor of the class has only one

The parameters of the Remotesamplelistener type.
The following properties affect batch and statistical modes.
Num_sample_threshold: number of samples in a batch (default is 100).
Time_threshold: The number of milliseconds to wait (default is 60 seconds).
Reference Address: http://jmeter-plugins.org/wiki/PerfMon/

5. Distributed Stress Testing

Jmeter is a Java application that consumes a large amount of CPU and memory, so when you need to emulate thousands of concurrent users, it is a bit of a struggle to emulate all concurrent users with a single machine, or even cause

Java Memory overflow error. In order for the JMeter tool to provide greater load capacity, JMeter has a mechanism for using multiple machines to generate loads simultaneously.

If the performance of the machine running the JMeter client does not meet the test requirements, the tester can control multiple remote JMeter servers through a single JMeter GUI client to stress test the server.

Simulate a sufficient number of concurrent users. By running JMeter remotely, testers can replicate tests across multiple low-end computers, which can simulate a larger server pressure. A jmeter GUI client instance,

In theory, you can control any number of remote JMeter instances and collect test data from them

By running JMeter remotely, testers can replicate tests across multiple low-end computers, simulating a larger server pressure, a JMeter client instance, and theoretically controlling any number of remote

JMeter instances and collect test data through them. In this way, you have the following features:

* Save test sample data to local machine
* Manage multiple JMeter execution engines with a single machine.
* It is not necessary to copy the test plan to each machine, and the JMeter GUI client will send it to each jmeter server.
* Each JMeter remote server performs the same test plan, JMeter does not load balance during execution, and each server runs the test plan in its entirety.

                                                          distributed test architecture

Terminology
Before we dive into the step-by-step instructions, it's a good idea to define the terms and make sure
The definition is clear.
Master–the system running Jmeter GUI, which controls the test
Slave–the system running Jmeter-server, which takes commands from the GUI and send requests tothe target system (s)
Target–the webserver We plan to stress test

Steps:
1.Slave: On the Slave server, go to the Jmeter/bin directory and execute Jmeter-server.bat on the WIDNWOS system (Jmeter-server on Unix).

2.Master: In the master server as the console, in the Master System, go to the Jmeter/bin directory.
2.1. Open the Jmeter.properties file with text editing
2.2. Edit remote_hosts=127.0.0.1
2.3. At the Remote_hosts=slave server address, the SLAVE2 server address,......
2.4. Open the Jmeter.properties file, set the Mode=standard (default) after setting the Mode=batch, if you do not modify mode mode, there may be concurrency after result view tree cannot collect the response data. (Configuration is located in the remote batching configuration plate)
2.5 Start JMeter

Distributed test Server environment under 5.1.Windows:
Linux slave:192.168.238.128,192.168.238.131
Win10 master:192.168.238.103
5.1.1. Configuring remote server Slave (jmeter-server)

(1) After extracting the JMeter, copy to the remote server (Linux/window), open jmeter-server. After the command window pops up, and you cannot close the window. By default, the port on the remote server is 1099,

If the port is occupied, you can set up a different port. In the JMeter directory: \apache-jmeter\bin\ find the Jmeter.properties file below.

The default port is 1099, no more configuration changes, if you choose to change to another port, you can find the server_port=1099 after editing the file, and change to the unused port as required.

.

5.1.2. Add the IP address of the remote server to the control-side master properties file in the steps:
1. Modify the Jmeter.properties file
2. Modify the Remote_hosts configuration
3. Modify the Mode=standard configuration

The detailed steps are as follows:
(1) under the JMeter directory: \apache-jmeter\bin\ find the Jmeter.properties file below.
After editing the file, locate the Remote-host in the remote hosts and RMI configuration palette and, as required, add the IP and port number of the remote server to add multiple remote servers. Example: remote_hosts=localhost:1099,localhost:2010

(2) in the Remote batching configuration plate will mode=standard in front of the # removed or modified to become mode=batch, if you do not modify the # in front of mode, may not be collected to slave server

The concurrency data.

Batch: sends the saved sample results when the counter or time exceeds the threshold value.

5.1.3. Running the console (2) in JMeter, click the Run-remote Start all menu to perform the remote server task

(3) After viewing concurrency, view the sample result data in the results tree.

(4) View response data in the results tree

The above is the practice of distributed testing under the window platform, in which the response data is viewed in the last view result tree, indicating that the concurrency is successful.

Distributed test pre-requirements under 5.2.Linux:
1. The JDK must be installed under the Linux (CENTOS7) server.
2. Close the FIREWALLD.
The 3.Linux and window networks must be accessible and within the same LAN.

Server environment:
Linux slave:192.168.238.128,192.168.238.131
Win10 master:192.168.238.103
5.2.1. Configuring remote server Slave (jmeter-server)

Linux as a server, before running jmeter-server, you need to install the JDK, installed into the jmeter of the entire file copy to the servers, this case is to copy the apache-jmeter-3.0 file to the Var/ftp/pub directory.

When you enter the./jmeter-server command in the/var/ftp/pub/apache-jmeter-3.0/bin/directory, an error occurs when you run the JMeter service.

Tip: Server failed to start:java.rmi.RemoteException:Cannot start. LocalHost is a loopback address.

Enter the command cd/etc into the directory, and then enter the VI hosts to edit the Hosts file, the IP address inside to modify the cost machine address, and then save.

You need to enter the command in the Bin directory:./jmeter-server-djava.rmi.server.hostname= the native IP address. To start successfully, you need to enter Ps-qa | grep jmeter-server Command or

Enter the NETSTAT-NTLP command to see if the operation was successful. or modify the configuration in the Jmeter-server, configured as follows:

Enter the vi jmeter-server command to edit the file and add it to the file

rmi_host_def=-djava.rmi.server.hostname=192.168.238.131 #IP地址是本机的地址.

5.2.2. The IP address of the remote server is added to the control-side Master Properties file

(1) Open the Jmeter.properties file in the apache-jmeter-3.0 directory and edit it. Locate the remote_hosts in the configuration file, and then add the remote server IP address and port.

For example: remote_hosts=192.168.238.131,192.168.238.128 If you need to add more than one server, it can be configured with commas separated. When the configuration is complete, open the client Apachejmeter console.

(2) in the Remote batching configuration plate will mode=standard in front of the # removed or modified to become mode=batch, if you do not modify the # in front of mode, may not be collected to slave server

The concurrency data.

After opening the console, view run-. Remote boot-The IP address of the remote server machine can be seen.

5.2.3. Running the console (3) in JMeter, click the Run-remote Start all menu to perform the remote server task

(4) After performing the task, review the log of the service side (Slave). The service-side program produces a starting and finished record.

(5) After viewing concurrency, view the sample result data in the results tree.

(6) View response data in the results tree

The above is the practice of distributed testing under the Linux platform, in which the response data is viewed in the last view result tree, indicating that the concurrency is successful.

Precautions:

In some cases, the firewall may still beblocking RMI traffic.

Symantec Anti Virus and Firewall

In some cases, Symantec firewall needs Tobe stopped from Windows services.

1. Open Control Panel

2. Open Administrative Tools

3. Double click Services

4. Go to the Symantec Anti Virus, RightClick and select Stop

Windows Firewall

1. Open Network Connections

2. Select the network connection

3. Right click and select Properties

4. Select Advanced tab

5. Uncheck Internet Connection Firewall

Linux

On Suse Linux, IPChains was turned on Bydefault. For instructions. Refer to the "Remote testing"

In the user manual.

On RedHat (or derivatives), iptables (NetFilter) was turned on by default. Execute "Service Iptables

Stop "to stop the Linux netfilter firewall.

Reference Address:

Http://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.pdf

Http://book.51cto.com/art/201204/327427.htm

6. Interface Test 6.1.WCF test test background:
There is a WCF interface in the gas station, which modifies the status information of the gas station by using the Putnetworkstatus method of the interface. The Putnetworkstatus method has two parameters, one is Mcumapid, and the other is status. If the method that invokes the interface succeeds, the true information is returned.

Test steps:
Before you test WCF, you need to get to the address of WCF, for example: http://10.190.130.70:8072/ServiceForEXS.svc?wsdl
The WCF protocol is the SOAP protocol, so a SOAP UI tool can be used to generate the XML script.
6.1.1.SOAP UI Generation XML

Open the SOAP UI tool, create a new SOAP project, and enter in the initial WSDL input

HTTP://10.190.130.70:8072/SERVICEFOREXS.SVC?WSDL Click the OK button.

When you click the OK button, you see the full method name of the WCF interface.

Open the window to the right after double-clicking Putnetworkstatus.

6.1.2.SOAP UI Test Interface

Will? To replace the test parameters, the Mcumapid parameter date is the mcuid of the gas station, and the status is the state of the gas station, 1 is disconnected, 0 is normal.

The status of the gas station MCUID to 1000122 before testing is disconnected.

After clicking the Run button, after successful operation, you can see the response data of the server in the right box to see the expected return value.

Check the status of the gas station on the page and show normal.

6.1.3.JMeter Testing In addition to the use of SOAP UI tools for interface testing, of course, you can also use the Apache JMETER
SOAP/XML–RPC the request for interface testing and concurrency testing.

After opening the JMeter interface, create a new threadgroup.

After selecting the thread group, right-click the popup menu->add->sampler->soap/xml-rpcrequest.

Copy the appropriate data.

Copy the corresponding data to the SOAP/XML-RPC request interface.

After selecting the thread group, the right-click menu->add->listener->viewresults Tree

Click the Run button.

View Samplerresult information in the View Results tree.

View the request information in the View Result tree.

The response data is the result of the expected return.
The above is the interface test for WCF, while the concurrency test can be parameterized and the concurrency settings of the parameter HTTP are tested.

6.2.WEB API test test Case:
1. When the client invokes the Web API, after sending the parameter request, the Web API receives the request, queries the order data according to the parameters sent, and then returns the order data to the client.

Invoking the Web API processing process

6.2.1. Test Preparation Note: Before the test needs to be confirmed with the developer, the method of testing which interface, what the parameters of the method, and whether the data involves encryption, the requested header has no additional data attached. 6.2.2. Creating a JMeter Script

The method of this Test interface

The method address of the test is: Api/values/getenquiry and the parameters sent are mainly stored in the header. Then let's make an interface call to the simple test Web API below.

After you open JMeter, create an Thrad group under Testplan, and then create the HTTP Header manager,http reqeust,view Results tree, respectively, under the thread group.

6.2.2.1.Thread Group is set in the Thread group, 2 seconds and 10 users, only a loop.
6.2.2.2.HTTP Header Manger

Add the requested parameters to the HTTP Header manager. Note the Content-type request value, and the value of the different request settings is not the same.

6.2.2.3.HTTP request sets the parameters of the HTTP request, Server Name of Ip,port number, method, and path. Special attention needs to be paid to how method is requested.
6.2.2.4 View Results Tree Adds the view result tree to view the results of the request and response.
6.2.2.5. Running tests

Click the Start button to run the test, and after running the results, click Viewresults Tree to view the results.

6.2.2.6. Viewing test results

In the View Results tree, after you select a result, look at the ResponseData data to check whether the returned number results are correct and the expected result. Note: Although the display is the correct tag, it does not represent the correct data.

This means that the test process status and procedures are correct, but do not represent the correct data. In addition to viewing responsedata, you can also view data for sampler result and result.

View the user's response time in response Timer VS threads. This feature is required to install plug-ins only. If more detailed test results are required, you can add more element components to the test as needed.

The 7.WEB API transmits JSON data in JSON format to the Web API side, and in JMeter there are two ways to do this, one in parameters
Input JSON data directly, and the other is to enter JSON data in the body. The following is a Web API project implemented in two different ways to transfer JSON-formatted data. It is also necessary to note that although these two methods can solve the problem of JSON format data, it is also possible to test the method of setting the name and value in the parameter of the HTTP request in accordance with the previous method of sending data.
7.1. Method 1 Enter the JSON data in the Parameters option of the HTTP request.
7.1.1. Adding the thread Group

Add a thread group to set the number of concurrent quantities as required.

7.1.2. Setting HTTP header Manager because of the need to get token authentication in the HTTP header in the Web API, it is necessary to set the token value on the head, and also to transmit the JSON format data, which must be set in the header content-type= Application/json, otherwise, will cause a transmission data error. 7.1.3. Add an HTTP request to add data in the HTTP reuqest that is transmitted in JSON format without entering data in the Name column. The data format is:
{key: "value", Key2: "Value2",......}
7.1.4. Adding a view result tree finally adds a listener view result tree to view the data and response data that sent the request
7.1.5. Running a test plan view results

View the data of the sampler in the View Result tree and examine the data for the reponse header.

View the JSON format data and request header information for post on the Request tab in the View Result tree.

View the Response Data tab in the View Reuslt tree to respond correctly.
The above is the test method of entering JSON format data into the Web API in HTTP request.

7.2. Method 27.2.1. Add Thread Group

Add a thread group to set the number of concurrent quantities as required.

7.2.2. Setting the HTTP Header Manager

Due to the need to obtain token authentication in the HTTP header in the Web API, it is necessary to set the token value on the head, and also to transmit the JSON format data, which must be set Content-type=application/json in the header.

Failure to do so results in a transmission of data errors.

7.2.3. Adding an HTTP Request

In the Body Data tab of HTTP Reuqest, add data that transmits JSON format. The data format is:

{key: "value", Key2: "Value2",......}

7.2.4. Add view result tree listener finally add a listener view result tree to view the data and response data that sent the request
7.2.5. Running a test plan view results

View the data of the sampler in the View Result tree and examine the data for the reponse header.

View the JSON format data and request header information for post on the Request tab in the View Result tree.

View the Response Data tab in the View Reuslt tree to respond correctly.
The above is the test method of entering JSON format data into the Web API in HTTP request.

8..IP cheat recently in the use of jmeter for stress testing need to use similar to LoadRunner IP spoofing function, after the degree of satisfaction Niang no fruit decided to again patient study JMeter official documents, Finally found in jmeter2.5 more than the version of the implementation of this feature, because the discovery of many netizens are looking for the answer to this question, so the test process to record down to help more students

8.1. Preparation work 1, window7 One, install jdk1.6 environment, here is no longer cumbersome to tell.
2, download the latest JMeter 2.11, link address: http://jmeter.apache.org/download_jmeter.cgi, download Zip package decompression can, double-click Bin/jmeter.bat start jmeter;
3, the use of IP spoofing must have a number of local IP available, usually the ordinary PC only one physical network card, which requires us to manually set up multiple IP binding the same network card:
A, Start menu, Control Panel, network Sharing Center, change adapter settings, local link
b, right-click Local link, properties, select Internet Protocol version 4 (double-click open window), if the use of automatic acquisition of IP, you have to manually set the IP
C, select the Advanced button in the Properties window, select IP Settings, click Add, enter a new IP address (you should be aware that there is no IP conflict in the LAN, you can ping the IP in advance to find no use), but the subnet mask must be consistent.

4, set up a number of IP can start using JMeter IP spoofing, it is important to note that so far, based on HTTP requests must use the HTTPCLIENT4 party can be successful.

First we save the set up IP in the CVS file so that we could import it into the JMeter parameter:

5. Add configuration components and configure IP parameters in the JMeter test plan

6. Adjust the HTTP request

For each HTTP to be set again, JMeter at the beginning of each concurrent thread from the file to take an IP value;
Test results:
The results can be viewed from the service side through the log, or through the JMeter view results tree to see the effect:

9. Reference to Appendix 9.1. Glossary of Terms (1) Aggregate Graph Collection Report

The meaning of the chart is described below:
Label: Description is the request type, such as Http,ftp.
#Samples: The number of samples in the graph report, the total number of samples sent to the server.
Average: The average of the graph report, which is the total elapsed time divided by the number of requests sent to the server.
Median: The middle value in the graphical report, which is the number representing the time, half of the server response time is below that value and the other half is above the value.
90%line: means that the response time of the 90% request is smaller than the resulting value.
Min: Is the number representing the time, which is the shortest time the server responds.
Max: Is the number representing the time, which is the maximum time the server responds.
error%: The percentage of errors requested.
Throughput: This is the throughput in the graph report, which is the number of requests processed per unit of time for the server, and note that it is seconds or minutes.
Kb/sec: Is the number of bytes requested per second.

Usage Analysis:
During the testing process, the average response time is an important measure of our performance testing, but in the test, especially in the aggregation report, the 90%line, I refer to the "LoadRunner didn't tell you"

One-descriptive statistics and performance results analysis, I think 90%line equivalent to the author's 90% response time, this value for our performance test analysis is also very useful. 90% response time is said in the Send

Request, 90% of the user response time is shorter than the obtained value, also shows that a system in the application, 90% of the user response time can reach this value, then for the performance analysis of the systems provides a good

Reference value.

Reference Address: http://blog.163.com/huo_jintao/blog/static/6152838020090130331286/

9.1.1. Monitoring server Image Plug-in

PerfMon Server Agent Plug-in: https://jmeter-plugins.org/wiki/PerfMonAgent/

Older versions of plugins: https://jmeter-plugins.org/downloads/old/

9.1.2. Using plug-in management to download plug-ins in the JMeter tool, in fact, in addition to the functionality of the tool itself, but also not meet the requirements of testing, you can use plug-in features. To use the plug-in management feature, you must download the JMeter Plugins Manger.jar package.
9.1.2.1. Download the plug-in Management Pack JMeter Plugins Manage.jar Package: https://jmeter-plugins.org/wiki/PluginInstall/

After the download is successful, the file needs to be copied to the JMeter lib/ext directory.

9.1.2.2. When the plugin management interface starts JMeter, click on the "Options" menu and select the Plugins Manager menu.

After opening the JMeter Plugins Manager interface, 3 tabs are displayed:
Installed Plugins: Displays the plugins that have been installed.
Available Plugins: Displays the plugins that can be downloaded.
Upgrades: Displays the plug-in that can be upgraded.
9.1.2.3 Download Plugin

On the Availableplugins tab, after selecting the Kafkasupport plugin, click the ApplyChanges and Restart jmeter button to start the download maliciously.

The download process, the speed is very slow, need to wait patiently, even may download unsuccessful, need to wait patiently and retry the download multiple times.

9.2 Starting Jmeter-server under CentOS is a hint: Server failed to start:java.rmi.RemoteException:Cannot start. Localhost.localdomain is a loopback address. Workaround 1:
Http://stackoverflow.com/questions/3150448/jmeter-loopback-address-error-when-launching-jmeter-server-on-linux

Under Linux server, set the environment variables:
Export Rmi_host_def=-djava.rmi.server.hostname=xxx.xxx.xxx.xxx
Or at run time, add parameters
./jmeter-server-djava.rmi.server.hostname=xxx.xxx.xxx.xxx
Or, add the following in the Jmeter.server file:
Rmi_host_def=-djava.rmi.server.hostname=xxx.xxx.xxx.xxx

Refer to the following articles:
http://blog.csdn.net/lcm_up/article/details/17594551
http://gmwen.blog.163.com/blog/static/18800705720116511927749/
https://voidtech.wordpress.com/2012/10/05/ Jmeter-fix-jmeter-server-server-failed-to-start-java-rmi-remoteexception-cannot-start-hostname-is-a-loopback-address /
9.3. Distributed testing in a Linux environment, there is no response data when viewing the response data in view result tree in the jmeter of the control side. Workaround:
In the Remote batching configuration plate, Mode=standard the previous # is removed or modified to Mode=batch, if you do not modify the # in front of the mode, you may not be able to collect the slave server concurrency data. Reprint Address: http://blog.csdn.net/Chris_111X/article/details/51966883

Distributed concurrency testing and Web API interface testing using JMETER3.0 combat