Mailingliste - Einträge 2005

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qftestJUI] the answer: -J-Xmx192m

  • Subject: Re: [qftestJUI] the answer: -J-Xmx192m
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 30 Dec 2005 09:44:31 +0100

Hello Joe,

thanks for the info. The error message was still based on the outdated
-mx... argument from previous Java versions. We had already corrected
that in the FAQ but overlooked the error message.

Increasing memory and following the other hints in the FAQ or the
error message is currently all you can do to prevent OutOfMemoryErrors
in very-long-running tests. But if you do follow them, use compact
logs and reduce the number of logs to keep, you should be able to
perform pretty large tests.

Does your SUT print lots of debugging messages during operation?
Buffering these in qftest currently appears to be one of the main
memory eaters.

In the future it will be possible to save partial test-runs as
separate run-logs, thus freeing the memory. The complicated question
here is: How to find the right balance so that use of run-logs remains
convenient and logs don't get scattered all over the place?

Best regards,

"Joe Greene" <joe.greene@?.com> writes:

>    -J-Xmx192m is the parameter format.
>    Your error message states: -J-mx192m
>    Thanks for your time.
>    ++meanjoe
>    [cid:image001.gif@?.48E89D80] Joe Greene
>    Premier Data Services
>    Quality Assurance/Customer Support
>    [1]joe.greene@?.com
>    303-316-3732
>    800-210-9100

Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH           
Tulpenstr. 41                                Tel: +49 8171 919870
DE-82538 Geretsried                          Fax: +49 8171 919876