Hi All,I am facing an issue during the replay of a script.During replay in response of web_submit_data and some web_url some invalid redirections are happening to some css ,jsp and jss files URL which is causing HTTP 404 since these redirects URL's are not correct.In tree view of the replay it is clearly visible that only for replay these redirections are happening but for record tree view these redirection are not present.The URL of these unwanted redirections is not at all related to content of the response.Could you all suggest something to remove these unwanted redirections.Thanks in AdvancePriyanka--
You received this message because you are subscribed to the Google Groups "LoadRunner" group.
To unsubscribe from this group and stop receiving emails from it, send an email to LR-LoadRunne...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Ask yourself, why would your website be presenting back 302, 303 or 307 responses which would cause a redirect to occur? VUGEN Scripts do not define redirects, but they will honor them when returned by the server.
My hypothesis is that you have dynamic data on request lines which are no longer valid after the session has terminated. In your environment these dynamic elements are being handled as server redirects. Cnsider recording twice and examining the differences between the recordings to identify the dynamic elements which need to be addressed before a proper replay can take place.
James Pulley
http://www.loadrunnerbythehour.com/PricingMatrix
Honest, Effective, Onshore USA script development beginning at 19.95 per hour USD
Given the number of generations between when they were built and today you should be thankful that the scripts lasted so long. Your default position appears to be that these should just run forever. This needs to be re-aligned. A better potions would be that with any new release you should expect them to fail (unless this is a static web services interface) because of changes and updates made by developers. If it does run (and it doesn’t check for expected content on every page return) then be very suspicious. It it does run and does so successfully you should be elated.
It appears that its useful life has run its course and these need to be rebuilt.
I am reminded of something similar shared with me recently. A company had hired a firm to develop VUGEN scripts for BAC monitoring several years ago. The company was warned that the firm represented people of questionable quality but management at the company dictated that the firm be used because of an attractive per hour rate. Well, the same management became very suspicious when the BAC availability reports showed great uptime and response time for applications which had been offline for six months or more. It was only then that the management dismissed the firm for incompetence.
Until you have proven that it runs correctly assume otherwise. Simply running an old script may report a bunch of smiling faces, unicorns and rainbows but the truth may be that the script is totally broken.
James Pulley
“100 Scripts” This is an unsually high number for load and performance. If you are using this for functional testing, please consider QTP or Selenium which would be more appropriate.
Having noted the above, you could well be having 404’s in your web application but they are masked by the front end as an orphaned resource on a page that is not displayed. This happens quite commonly, but it is very visible in LoadRunner. Track the resource which is showing the 404 to the source on the page. Affirm that the resource is actually on the server. It may not be.
From: LR-Loa...@googlegroups.com [mailto:LR-Loa...@googlegroups.com] On Behalf Of Priyanka
Sent: Thursday, February 21, 2013 5:16 PM
To: LR-Loa...@googlegroups.com
Subject: Re: Unwanted redirection happening in response of web_submit_data and web_url
Hi All,
As I already mentioned in my second reply that same HTTP 404 is observed even while recrding the same flow again and replaying it.
So this issue is not because of the old scripts.Also all scripts are modified after each release for any chages added to the application.
Since recording 100 scripts for each release does not fit into the time line ,we do not record the same script same script again and again for each release.
We do follow a process of having mock runs, clean up of logs and data related clean ups after every release.
And I believe that it is very difficult to re-record new script in every month for regression suites which consists of a large number of scripts.
The same HTTP 404 are occuring for newly recorded script as well and same error situation is not replicated by manual hit.
Since it is only occuring through load runner script run and that too the URL's for which error occurs are not related to application.
I kindly request you all to provide some valuable suggestion.
Hello Priyanka,
Check if you have some "extrares" in you web_submit_data.
If yes try deletin them and running the script again. That might be the cause of the failure.