LoadRunner timeout and error

LoadRunner defines the "Response Time" from the client perspective. When a client request is sent, LoadRunner starts to calculate the response time until it receives the response from the server. At this time, the problem arises: if the server Queue is full and the server resources are busy, the request will reside in the server thread. In other words, this new request does not really load the server, but unfortunately, the timer of the request has been started, so we can easily predict that, the response time of this request may become long, or even long, cause the request to fail due to timeout. After the test is complete, we can check the results and find this unfortunate phenomenon: the average transaction response time is very long, and the gap between the minimum response time and the maximum response time is very large, at this time, the average response time actually loses its meaning. That is to say, because the request sent by the client is too fast and affects the actual measurement result, setting the step size can alleviate this situation. In this case, you should try setting pacing and then run it to check the situation.

Timeout often occurs during the playback of Web protocol scripts. There are also many causes of errors and the solution is different.
　Error 1:Action. C (16): Error-27728: Step download timeout (120 seconds) has expired when downloading non-resource (s ).

　　Error analysis:For the HTTP protocol, the default timeout value is 120 seconds (which can be modified in LoadRunner). The client sends a request to the server. If no result is returned for the server after 120 seconds, a timeout error occurs.

Solution:First, set the timeout value in the running environment. The default timeout value can be longer, and then set multiple iterations. If there is a timeout, you need to set the "winlnet replay instead of sockets" option in the "RunTime setting"> "Internet Protocol: Preferences"> "advanced" area, and then check whether the playback is successful.

　　Error 2:Action. C (81): continuing after error-27498: timed out while processing url = http: // 172.18.000070: 7001/workflow/bjtel/leasedline/querystat/suborderquery. Do

　　Error analysis:This error is often caused by high concurrency pressure and the server side being too busy to respond to client requests in a timely manner. Therefore, this error is normal and is caused by high stress. If the stress is low, this problem may occur. It may be because there is an error in the script somewhere. Check the script carefully and the error message will locate the location where a specific problem occurs.

　　Solution:For example, the above error is located on a URL. You need to run the scenario again and access the URL on other machines. If it cannot be accessed or takes too long, it may be that the server or the application cannot support such a large load. Analyze the server and optimize its performance.

If there is still timeout after the scenario is run again, analyze the causes in various graphs, such as checking whether there are problems with the server, DNS, and network.

Finally, add the runtime timeout settings. In "run-time settings"> "Internet Protocol: Preferences", click "options ", increase the value of "http-request connect timeout" or "http-request receive.

 

Http://shop104965075.taobao.com