Highlighted
Absent Member.
Absent Member.
1472 views

Load Runner: Error in Correlation

Hi All,

Need your inputs on below issue:

User interface: BOXI 3.1 Infoview opendoc.

Phase: Performance testing
Tool: HP Load Runner 9.1. (LR)
Issue in parameter: Correlation

We need to perform PT for 120 users as part of project requirement. As there are many web links that are traversed while browsing report in Infoview (login, prompt, default view, drill etc) we have used automated correlation so LR can keep track of changing session ID.

LR script is working fine with 25-35 users and beyond that it starts throwing an error “Error -26377: No match found for the requested parameter "WCS_param6". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 1024 bytes, use web_set_max_html_param_len to increase the parameter size”

Additional inputs may be helpful to analyze

1. Without use of correlation the response time of transactions is too very low (.001sec) and is not realistic.
2. web_set_max_html_param_len is already increased to 262144 bytes. (gives same error again on increasing the number of users).
3. Due to many traversal of links (in between there are many blank pages) we are unable to view the report execution in Run Time Viewer of Load Runner.

Please share inputs from your experience of load runner with BO Infoview reports. Also if you have any reference to MANUAL CORRELATION please let us know.

Any pointers for resolving the issue will be highly appreciated.

Thanks,
Ankit
0 Likes
7 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Load Runner: Error in Correlation

Hi Ankit,

1. Ensure you are setting think time and pacing accordingly for the number of users.
You could also limit the think time to 3-5 secs.

2. I understand you are running auto correlation, which may not pick all the necessary correlation.

3. To start with manual correlation, Record 2 scripts for same business process and compare the dynamic values with WDiff.
Correlation is applicable only to those values which fall under server response.

4. Refer chapter 54 of the Vugen guide under Documentation for manaul correlation in Web.

Hope this helps



0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Load Runner: Error in Correlation

Hi

Thanks for your response.

#1 is already taken care.
#3 we started with same approach (2 version are recording and replay time) but in script when we right click and try to convert to parameters, the option is coming as inactive and not allowing us to replace few instances with parameters. Following are 3 instances observed by us &ses, &jsessionid and &sEntry which differ over time.

Also we are using correlation studio for auto testing. is this fine?
#4 Please help us by refering to the link of this guide.

Thanks.
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Load Runner: Error in Correlation

Hi Ankit,

What I meant with recording 2 scripts is
record 1 script with business process and save sample1.usr.
Bring up another script record business process all over again and save sample2.usr

Goto tools->compare with script and compare action segments of either scripts(if recorded in action()).
This should show you differences in the script. for every dynamic value that you encounter check whether the value is on response(see generation log).


For vuser guide.
Goto start->Loadrunner->documentation->Vugen user guide, chapter 54
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Load Runner: Error in Correlation

try putting web set max in init().

you also can get the correlation boundaries thourgh extended log - response from server.
0 Likes
Highlighted
Established Member..
Established Member..

Re: Load Runner: Error in Correlation

If your script runs for 25-35 users and after that if it fails then I don't think there is problem with the correlation part. Did u check ur correlated values?? is it really so huge in size??
u problem might be in the data(parameter file)if u r not using more than one data in parameter file.
Next u check manually check the application when u r running ur loadtest and see when u r getting those errors that time u r manually able to see those pages where those errors are coming.

hope this will help u to pinpoint the problem area.

Thanks,
Prasenjit
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Load Runner: Error in Correlation

Hi,

We tried using the manual correlation and when compared 2 scripts the changes are found at 3 places. When we try to parameterize the below changes, we are unable to find the code in server response or â create parameter linkâ is inactive.

sEntry
Jsessionid
&ses

Please suggest if protocol Web(HTTP/HTML) is valid.

Thanks,
Ankit

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Load Runner: Error in Correlation

Hi Ankit,

If comunicating over HTTP then Web(HTTP/HTML) is correct.

You need to correlate the above values if you can trace them in Response body in generation log.
You will have to use web_reg_save_param(). F1 on this function to know the attributes.

Hope this helps.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.