First thing "Server xyz has shut down the connection prematurely " is not a webserver issue.
This is purely load runner issue and is one of the major pain area.
Try Following:
1. Make sure we are not ramping up all user simultaneously
2. Rendezvous point is not holding up too many users.
3. Make sure retry option is greater than 5
4. Check network connectivity or blockage.
5. Decrease the load from load runner machine
6. Clear the Temp folder in (Documents and Settings-->user-->Local Settings)-->Temp
and restart the machine on which LoadRunner is installed (This one is my favorite, it has always helped me in getting rid from this error, but the condition is that scripts ran successfully before and now you suddenly start seeing this error)
7. Recently I observed that if we suddenly start seeing this issue, then best option is to restart all machines and servers in your network or load test domain. I cant explain the reason behind it, but it works :)
Put this in script, not a solution but just the workaround.
web_set_sockets_option ("NEW_BEHAVIOR_OF_OVERLAPPED_SEND", "1");
If none of the above option helps then put web_set_sockets_option("IGNORE_PREMATURE_SHUTDOWN", "1"); in vuser_init()
You can also following
Run time settings --> Preferences --> Use WinInet Replay instead of Sockets (windows only)
but it worked in very specific cases. Not a general solution.
Note: Point 3 :" Make sure retry option is greater than 5 " is applicable only for Oracle 10g application.
This is purely load runner issue and is one of the major pain area.
Try Following:
1. Make sure we are not ramping up all user simultaneously
2. Rendezvous point is not holding up too many users.
3. Make sure retry option is greater than 5
4. Check network connectivity or blockage.
5. Decrease the load from load runner machine
6. Clear the Temp folder in (Documents and Settings-->user-->Local Settings)-->Temp
and restart the machine on which LoadRunner is installed (This one is my favorite, it has always helped me in getting rid from this error, but the condition is that scripts ran successfully before and now you suddenly start seeing this error)
7. Recently I observed that if we suddenly start seeing this issue, then best option is to restart all machines and servers in your network or load test domain. I cant explain the reason behind it, but it works :)
Put this in script, not a solution but just the workaround.
web_set_sockets_option ("NEW_BEHAVIOR_OF_OVERLAPPED_SEND", "1");
If none of the above option helps then put web_set_sockets_option("IGNORE_PREMATURE_SHUTDOWN", "1"); in vuser_init()
You can also following
Run time settings --> Preferences --> Use WinInet Replay instead of Sockets (windows only)
but it worked in very specific cases. Not a general solution.
Note: Point 3 :" Make sure retry option is greater than 5 " is applicable only for Oracle 10g application.
No comments:
Post a Comment