10061 can point to many reasons, from invalid session handles to bad
addresses. Session management can be a critical thing in a load balanced
environment. I guess as a way of introducing a control point, do you have
any load generator from which the script works as expected?
James Pulley, http://www.loadrunnerbythehour.com/PricingMatrix
Hi,
Thanks
Deb
--
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 looks like a proxy issue to me. Take a good look at the proxy
settings for both browser and load generator. If they match this
should simply not happen.
Another thing to test here is to open the command line and run 'telnet
host port' (replace host and port with the correct host and port, of
course) to see if the machine you run that command from can actually
connect to the target. If it can't you should get the same error -
connection refused.
This does point out an interesting issue though - if your browser
connects through a proxy the load generator may be forced to do the
same thing. But that means that if you start loadtesting you will
start putting load on that proxy server as well. You may need to make
arrangements for monitoring it and probably talk to whichever party is
responsible for maintaining it as that proxy server probably has
production status.
Secondly you may have to start thinking about the question "Is it
typically the case for normal users to connect through that proxy?".
If the answer is 'no', then ideally you should try to find a way to
connect to the application under test without it.
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
I would try to remote desktop to the load generators and instal and run vugen from these boxes with the same scripts or try to record a fresh one there and see if it is possibleb and what the run time settings are showing you. If all else fails get the networking team involved and describe your dilema and see if they need to modify your DNS settings on your generators. Hope this helps, Roland
Not really. Your network path seems to work as the connection is
accepted, but the proxy server then fails to answer.
This looks like a configuration problem on the side of the proxy
server or something along those lines. You'll need to talk to whoever
administrates that machine. That person can look at logs and tell you
perhaps why it is dropping your connection.