LoadRunner test Results specific Analysis :
A Error message Analysis
Analysis Examples:
1. error:failed to connect to server "172.17.7.230″: [10060] Connection
Error:timed out Error:server "172.17.7.230″has shut down the connection prematurely
Analysis:
A, the application service dies.
(Small User: A problem on the program.) The problem of processing the database on the program, the actual test is mostly the configuration problem of the server link.
B, App service is not Dead (app service parameter setting problem)
The maximum number of links corresponding to Apache and Tomcat needs to be modified if the connection is received
Connection refused message, stating that should increase the corresponding server maximum connection settings, the increase in accordance with the actual situation and server hardware, the proposed increase of 25% each time!
C, the connection of the database
(Maximum number of connections initiated by the database (related to hardware memory))
D. The maximum number of links that our application spring controls is too low
2. Error:page download timeout (seconds) has expired
Analysis:
A, the application service parameter setting too big causes the server bottleneck
B, too many pictures on the page
C, in the Program processing table when the check field too much
D, the actual test some resources need to request the external network, and our test environment is the LAN environment
3. Error "Http://172.17.7.230/Home.do ..."
Analysis:
A, the script design error, caused the page exception. The server is responding!
B, the concurrency number is too large, causing the server response delay.
4. Error page "Text=xxxxx"
Analysis:
A, scripting design issues, for example, the previous script modified some content, resulting in subsequent script access exceptions.
B, uncertainties, sometimes playback of the normal script, one in the scene in the case of such errors. You can only modify the script repeatedly!
LoadRunner11 Study record Five