User (firstname.lastname@example.org) posted:
Here is my environment:
Server Platform: Win2k with Java Servlets returning html and xml data
Mix of MSSQL and Oracle dbases
Occasionally when the components in the database crap out due to
unavailability etc. IE returns Error or Warning Messages pop-ups.
I've disable script debugging in the browser - During replay
occasionally, these pop-ups randomly appear and the only way that the
script cpmpletes is if I intervene? How do you write an error
i.e -- an auto clicker to those OK buttons. What I want to achieve is
that the vuuser just don't error out and follow a logic of navigation
and persist through these error boxes.
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Small business owners...
Tell us what you think! http://us.click.yahoo.com/vO1FAB/txz...SFAA/NhFolB/TM
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
User (JosephH614@aol.com) posted:
Content-Type: text/plain; charset="US-ASCII"
Try using the function web_set_max_retries to retry the step. This function
will tell LR to keep trying the step x number of times.
Additionally, if the step fails all x number of times, you can create an
if/else statement and have LR abort the iteration (not the entire vusers) and
begin with the next iteration (you will want use rc=web_set_max_retries in
creating your if/else statement).
See the LR help and the LR knowledge base/discussion group for tips.
Content-Type: text/html; charset=US-ASCII
< !-- |**|begin egp html banner|**| -->
Well, the 1st thing coming to my mind is, -
in case you know the HTML context of the
error messages, - try to capture them.
You can use the correlation functions for
Have you tried creating your specific error handling routines?
-- Mike --
In the case of web_set_max_retries does something else need to be done other than placing the function before the action that you want to retry. Initially, I thought that this function would only work in the context of a scenario (like rendezvous points). However, even when run from a scenario and set to 10 retries, the action is not retried. The transaction fails. In this case, it is failing on a 500 error. I have set the debug level for this action to full trace. Thanks.