loadrunner A simple flow gets recorded using IE without...

  • Thread starter Pankaj Chandan Mohapatra
  • Start date

  • perf-test.com need your contributions to build up a strong repository of performance engineering resources.

P

Pankaj Chandan Mohapatra

Guest
A simple flow gets recorded using IE without any trouble but, while replaying the same it thows error "connection shutdown prematurely".One of the way to replay the script is to bypass the NTLM authentication by replaying it in Wininet mode. The question is ...is there any other way to replay it using socket mode apart from providing proxy and authenticating it with a username and passwrd?
 
Sort by date Sort by votes
try with this.. web_set_sockets_option("SSL_VERSION", "TLS"); enable proxy with appropriate port number and provide proper authentication..
 
Upvote 0 Downvote
Ram Lekkala where do I get the user name and passwrd from?? Do I need to ask the server admin to provide me the credentials or can we extract the information from Load runner itself?
 
Upvote 0 Downvote
Roylen Topno using that option only ignores the error mssge . It doesn't fix the root cause behind the error.
 
Upvote 0 Downvote
I want to put forth a different hypothesis. Your connection is not being broken due to authentication model, but due to an unhandled dynamic element in the stream which has expired and therefore is the root cause of the forced disconnect. Record your business process twice, taking care to clear the cache between each recording. Next, record with different credentials. Compare the recorded streams and you will likely find the root cause of your issue.
 
Upvote 0 Downvote
Pankaj Chandan Mohapatra: credentials should be your test id and pwd, there will be proxy url which will record by default.. you just enable use custom proxy and click use proxy server in runtime settings
 
Upvote 0 Downvote
Just Use the header web_set_sockets_option("SSL_VERSION","TLS"); You can also Use web_set_sockets_option("IGNORE_PREMATURE_SHUTDOWN", 1");
 
Upvote 0 Downvote
James Pulley I compared the snapshots of recording and replay ...the recording snapshot says that when the URL is hit for the first time it hits the proxy IP "X" then returns HTTP code 302 then it again hits a different URL with the same host and then it returns HTTP code 200. During the the replay it hits the original IP "Y" and hence returns "connection ends prematurely". So I went to add the Proxy IP in runtime settings and provided the test id and passwrd now when it hits the IP x it returns HTTP code 407 and the proxy connection closes.Now I recorded the same flow again....this time the recording snapshot shows that instead of hitting IP " X" it hits a completely new IP which in IPv6 format......and now I am struck.
 
Upvote 0 Downvote
My guess is that your "proxy" in this case is actually a load balancer with a virtual IP which is then handing you off to the server destination. I still maintain that you have a piece of dynamic data in the request, either state or time, which is dynamic and need to be addressed. This dynamic piece which has expired is the root of your forced disconnect, not the redirect from the load balancer with the virtual IP for the site. Get a visio diagram of your site architecture. This should help
 
Upvote 0 Downvote
You must log in or register to reply here.
Top Bottom
Back