--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
That particular error is pretty common. Apparently certain devices
implement http deflate compression slightly differently from what LR
expects, resulting in intermittent errors on some transactions, usualy
particular resource downloads.
While this forum discussion
(http://www.sqaforums.com/showflat.php?Number=550003) seems to say
resource starvation at the load generator side may be the cause, I
have never observed it in conditions where resource utilisation on the
generator was an issue.
There are several solutions to this:
1) Add the following line to the top of your script:
web_add_auto_headder("Accept-Encoding", "gzip");
This disables the 'deflate' compression method by defaulting to the gzip method.
2) Change the compression method in your runtime settings: Preferences
> Options > Accept server side compression. (May need some fiddling
before it works, I never seem to remember which options should be on
and which shouldn't be..)
3) Find the offending resource - usually a flash object or picture and
take it out of the offending transaction - either by removing it from
the EXTRARES section, or by means of web_add_filter(). Then put that
in it's own web_url() call, with the proper 'RecContentType' header
attached - eg. "RecContentType=application/x-shockwave-flash".
Why the last option seems to work for some applications beats me.
Frankly, it looks like a bug in Loadrunner - one that is a) very old
(these errors have been around since LR 8, at the least) and b) only
occurs in very specific circumstances that probably have never seen in
any HP lab.
Regards,
Floris
---
'Many people asked me if I was afraid to fly and implied that I should
have stayed home, close to family and friends. I replied that if I had
stayed home, the terrorists would have won.
Unfortunately, my government does not agree with my definition of
winning. They think that living in fear and trying desperately to keep
us all 100% safe while flying is the most effective way to fight
terrorism. It reminds me of a boss that told me he liked it when
people lived in fear of being fired, they worked harder. I told him
being fired held no fear for me. When you live in fear, you do
irrational things - like sending millions of people's shoes through an
xray scanner every day.'
-- Stormy Peters
1) Try to find in your logfiles which file or resource has this problem.
2) Then add a "web_add_filter()" call before the step where this
problem occurs to exclude that specific resource from the transaction.
3) If that makes the problem go away, add another web_add_filter()
call after the offending step to remove the filter you added earlier,
followed by a recording of the browser downloading that specific file
or resource (and nothing else).
A caveat - I have no idea how successful this option will be for your
specific case. I've only seen this tried once.