Recently a performance test for a Load Balancer project, using the LR Recording script Protocol as the HTTPS protocol, an error occurred while playing back the script:
[General_msg_cat_ssl_error]connect to Host ' XXX ' failed:[10054] Connection reset by peer [msgid:merr-27780]
LoadRunner default send is sent via sockets (convert HTTP to sockets), while sockets default SSL is SSL2 and SSL3. The HTTPS protocol recorded script will fail the sockets port connection when it is played back in SSL3 version , and the connection will be rejected by the server.
Workaround: set Run-time Setting
Locate the Internet protocol-preferences-advanced, and tick the "winlnet replay instead of sockets (Windows only)" option.
When this option is checked, LR uses the Winlnet engine playback script (only for windows). Winlnet is a Microsoft communication, its IE is based on this communication, Winlnet does not support UNIX, and the implied VUser line Cheng type is not accurate module network connection speed and the number of connections.
LR Replay HTTPS protocol script failed: [General_msg_cat_ssl_error]connect to Host ' XXX ' failed:[10054] Connection reset by peer [MsgId: MERR-27780]