1. The socket closed problem occurs:
Modification:
Cause of the problem : Under JMeter, when sending http requests, use keepAlive is generally selected by default (what is this? See the information later), this is the connection protocol, the JMeter pit is here, and this is checked by default (if not checked) If you select it, it will not be saved), but the time setting in its configuration JMeter.properties is logged out by default, which means that it will not wait. Once the connection is idle, it will be disconnected immediately, which leads to our stress test. The situation in which the transaction fails.
Solution : Modify httpclient4.idletimeout=<time in ms> and set it to a time that you think is reasonable. Generally, it can be set to 10-60s (meaning that the connection will be disconnected after 10s of idle time). Note that the unit here is ms. After the modification is completed, the pressure test is performed again, and the error is no longer there.
2. When the combination scene is large and concurrent, page redirection (obviously sending the correct request parameters, abnormal return results), null, 404 and other problems occur
During the stress test, the data was consistent and normal in the first 2 minutes. After fixing for 2 minutes, an error occurred in each transaction. It can be concluded that the server cannot handle the current so many requests. This situation does not occur in the actual situation. Consider adding thinking time. Add a fixed timer of 200ms (interval time of each request is 200ms), after modification, it will continue to run for 15 minutes without any problems
3. How to add reasonable thinking time? Does think time have an impact on throughput?
