Hi Mark,

with a repeat count of 100000 I'm not surprised at all that you get an OutOfMemoryError: I suppose that each of your entities contains a few steps and as a consequence, this makes a huge amount of steps that need to be kept in memory. Nevertheless you say that you get an OOM only when a step fails. Does it means that you've been able to let this run without OOM when not step failed?

Marc.

PS: with the coming changes (yes I know, I talk about these changes since too long) such huge suites should be possible without too high memory consumption (supposing that no report is generated) as the steps will be made available for garbage collection as soon as they have been executed.

Mark Levy wrote:
Hey Marc,

Here is the script code I am using. I am doing this in a use case file which calls the modules you see here:

                  <repeat count="100000">

                        &createProperties;

                        &startPage;

                        &travelerLookupLogin;

                        &createSingleAuthorizationStepA;

&createSingleAuthorizationStepB;
                        &createSingleAuthorizationStepC;

                        &createSingleAuthorizationStepD;

                        &indicateNoMultipleTDY;

                        &createSingleAuthorizationStepE;

&createSingleAuthorizationStepF;
                        &createSingleAuthorizationSandP;

                        &storeDocumentName;

                        &skipTripSegment;

                        &skipTripSegment;

                        &skipTripSegment;

                        &tripSummary;

                  </repeat>

Now, if any of these steps fail, say for example the title on one of the pages is one that is not expected or a button is not present, then I receive a Java heap error. This hurts me because I am trying to use this process to test for resource leakages on our server. Anyways, I would rather see this fail, so that I can debug as usual than try to clean up a Java heap error.

Thanks for your help,

Mark Levy

-----Original Message-----

From: Marc Guillemot [mailto:[EMAIL PROTECTED]

Sent: Friday, July 28, 2006 2:30 AM

To: Mark Levy

Subject: Re: [Webtest] Repeat step causing a Java heap error

Hi Mark,

please keep such discussion on the mailing list.

Seems strange. Can you provide the script code?

Marc.

Mark Levy wrote:

 Hey Marc,



Thanks for getting back to me.



 I understand the problem now.  The problem is that if you have a step

 that fails - for example if you try a <clickButton> step on a page

 which does not have a button - the test will not fail when it is

 nested in <repeat> tags.  Instead, the heap error is thrown.  This is

 also true when I try to place a <verify> step before the <clickButton>

since if the <verifyTitle> step fails, a Java heap error is also
displayed.



 Thanks,



 Mark





 -----Original Message-----

 From: [EMAIL PROTECTED]

 [mailto:[EMAIL PROTECTED] On Behalf Of Marc Guillemot

 Sent: Wednesday, July 26, 2006 2:24 AM

 To: [email protected]

 Subject: Re: [Webtest] Repeat step causing a Java heap error





 Hi Mark,



 which build do you use? I've fixed a memory leak for a few weeks.



 Marc.

This e-mail and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify me at (703)288-5300 and permanently delete the original copy and any copy of any e-mail, and any printout thereof.


_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to