Summary of problems encountered when LoadRunner performs performance testing

1. Action.c(4): Error -27796: Failed to connect to server "10.10.10.2:81": [10048] Address already in use
Try changing the registry value 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters\TcpTimedWaitDelay to 30
and HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters\MaxUserPort to 65534
and rebooting the machine
See the readme.doc file for more information

 

2.Action.c(4): Error -26610: HTTP Status-Code=502 (Bad Gateway) for "http://10.10.10.2:81/pa/newstock/hq/index.jsp"

 

 

3.Error: Exception was raised when calling event-notify Vuser function in extension lrwreplaymain.dll: System Exceptions: EXCEPTION_ACCESS_VIOLATION

Solution: Create a new TEMP directory under the C drive, set the value of the environment variables TMP, TEMP to C:\TEMP and it will be ok

 

4.   Action.c(33): Error: C interpreter run time error: Action.c (33):  Error -- Unresolved symbol : vuser_end.

 

 

5.Action.c(77): Continuing after Error -27728: Step download timeout (120 seconds) has expired when downloading non-resource(s)

Solution: Set the setting process of loadrunner9.1, run-time setting---internet protocal---preferences---advanced--open options--modify Step download timeout(sec) in General: 600.
This value Set according to your actual needs. My scenario here is to download an attachment, and the manual operation takes about 3.4 minutes.

 

6.Action.c(33): Error: C interpreter run time error: Action.c (33):  Error -- Unresolved symbol : vuser_end.

-------- means: syntax error in user_end part. For example, one of the following lines is missing:

user_end()

{

     return 0;

}

 

7.Connection to load generator failed.

Error: Process "lr_bridge.exe" was not created on remote host "192.168.170.161". Reason: communication error. Make sure the Agent process or service is running on the remote machine..    [MsgId: MERR-29987]

Error: Communication error: Failed to connect to remote host [server IP: 192.168.170.161].    [MsgId: MERR-10343

---------The reason is: use the controller to load another load machine, and prompt failed.

Solution: This happens because of restrictions within the firewall, etc. The load machine is Windows 2008, and LoadRunner 9.5 is installed. There is no additional firewall or anti-virus software installed on it. So turn off the windows firewall (control panel---firewall---off).

Summary of problems encountered with Loadrunner

Note: The following problems all appear in windows server 2003, loadrunner 11

Question 1:

Action.c(4): Error -27796: Failed to connect to server "ip:port": [10048] Address already in use
Try changing the registry value 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters\TcpTimedWaitDelay to 30
and HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\tcpip\Parameters\MaxUserPort to 65534
and rebooting the machine
See the readme.doc file for more information

Solution:

In the load generator registry HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters, there are the following two key values:

TcpTimedWaitDelay

MaxUserPort

1. The default value of TcpTimedWaitDelay here should be 30s, so here, reduce this value to 5s (adjust as needed).

2. You can also increase the MaxUserPort (if this value is not the maximum value).

 

Question 2:

Action.c(4): Error -27796: Failed to connect to server"ip:port": [10060] Connection timed out

Solution:

This problem is probably because the maximum number of connections allowed by the web container for accessing the application deployment is too low. I am using the tomcat container, so modify the tomcat configuration file server.xml as follows

      maxThreads="150"

................................. Change the maxThreads value to a larger value

By the way, explain the meaning of each attribute in the tag in tomcat:

<connector port="8080"    maxThreads=
      "150"     
      minSpareThreads="25"     
      maxSpareThreads="75"   
      acceptCount="100"   
      />   
  maxThreads="150" means to process up to 150 connections at the same time   
  minSpareThreads="25" means even if no one Using so many empty threads to wait for   
  maxSpareThreads="75" means that if you can empty up to 75 threads, for example, 80 people visit at a certain time, and no one visits after that, tomcat will not keep 80 empty threads, but close 5 empty.   
  acceptCount="100" When the number of simultaneous connections reaches maxThreads, it can also receive queued connections, and if it exceeds this connection, it will directly return to reject the connection.

 

Question 3:

Failed to Initialize. Reason: TimeOut

 

Question 4:

Failed to Run. Reason: TimeOut

 

Question 5:

Error: Communication error: Linked List client failed to initialize server pointer. The


server did not respond
2. There is no target to provide this service 3. Failed to send packets, the reason is
a communication error
4. It should be a failure to send and receive packets server down