In case you are dealing with HTTPS based/SSL enabled application, you should be reading this post very carefully as it help you to avoid any script replay failure caused due to HTTPs connections.
During replay of a script via an HTTPS connection to the SSL Web server, the vugen script fails with the following error:
"attempting to reuse saved session.........."
This error is caused due to an SSL session being reused. Information from previous handshakes is incorrectly put into the failing SSL handshake. To resolve this issue, you can reduce the amount of connections simultaneously opened to a Web server by using the following statement at the very beginning of the script:
web_set_sockets_option("MAX_connectionS_PER_HOST","1");
It has been found that changing the number of open connections does not cause a significant change in performance. Performance issues are more likely to be caused by other factors such as network congestion at a router/switch/hub than by the number of maximum connections allowed.
Not Working
ReplyDeleteThe thing helped me out - checked the winInet option under preferences tab in Run Time Setting...
DeleteCheck winlnet works, but if you use many users, it will start to fail, because timeout connection.
Deleteto eliminate this intermittent SSL and “not a socket” errors that occurs when replaying the LoadRunner scenario in the controller.
Modify your script(s) to include the following statements, these statement should be at the beginning of the script(s)
Vusert_int()
// Or
Action()
{
web_set_sockets_option("SSL_VERSION", "3");
web_set_sockets_option("MAX_CONNECTIONS_PER_HOST","1");
...
The first line web_set_sockets_option("SSL_VERSION", "3"); forces the SSL connection to use SSL version 3 instead of letting the server suggest a version during the connection handshake.
The second line web_set_sockets_option("MAX_CONNECTIONS_PER_HOST","1"); forces a single TCP connection to stay live between the Load Generator to the AUT servers. Ending the possibility of errors when LoadRunner sends data across that connection, if the server try to prematurely shutting down an existing connection
Performance Testing -You Can'T Improve What You Can'T Measure: Error: "--27776: Server "[Server_Name]" Shut Connection During Attempt To Negotiate Ssl Session" >>>>> Download Now
Delete>>>>> Download Full
Performance Testing -You Can'T Improve What You Can'T Measure: Error: "--27776: Server "[Server_Name]" Shut Connection During Attempt To Negotiate Ssl Session" >>>>> Download LINK
>>>>> Download Now
Performance Testing -You Can'T Improve What You Can'T Measure: Error: "--27776: Server "[Server_Name]" Shut Connection During Attempt To Negotiate Ssl Session" >>>>> Download Full
>>>>> Download LINK 6a
Many Thanks Smit, it worked with me.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteThis error we can avoid by making SSL version and cipher for SSL to be specified.We can add this function web_set_sockets_option("SSL_VERSION", "TLS"); at the starting of our script.
ReplyDeleteIts not necessary, this will work out every time. we need to know which SSl version to use.
Deleterefer below blog for more info on how to find ssl version and cipher-type : http://performancetestinglearnings.blogspot.ca/2015/02/how-to-find-ssl-version-and-cipher-type.html
Performance Testing -You Can'T Improve What You Can'T Measure: Error: "--27776: Server "[Server_Name]" Shut Connection During Attempt To Negotiate Ssl Session" >>>>> Download Now
ReplyDelete>>>>> Download Full
Performance Testing -You Can'T Improve What You Can'T Measure: Error: "--27776: Server "[Server_Name]" Shut Connection During Attempt To Negotiate Ssl Session" >>>>> Download LINK
>>>>> Download Now
Performance Testing -You Can'T Improve What You Can'T Measure: Error: "--27776: Server "[Server_Name]" Shut Connection During Attempt To Negotiate Ssl Session" >>>>> Download Full
>>>>> Download LINK