For long-running tests it's best to use non-GUI mode and as few Listeners as possible.
See: http://jakarta.apache.org/jmeter/usermanual/best-practices.html#lean_mean Also the Generate Summary Results Post-Processor is useful for keeping track of the progress of the test: http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Generate_Summary_Results On 31/01/2008, Wang, Harry <[EMAIL PROTECTED]> wrote: > The Graphic results, of course. That might explain it. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 31, 2008 12:40 PM > To: JMeter Users List > Subject: Re: JMeter stopped on Forever Loop > > Could have run out of heap space. Which listener(s) are you using? > Many listeners keep entire response history in memory. > > > > > "Wang, Harry" <[EMAIL PROTECTED]> > 01/31/2008 03:33 PM > Please respond to > "JMeter Users List" <[email protected]> > > > To > "JMeter Users List" <[email protected]> > cc > > Subject > JMeter stopped on Forever Loop > > > > > > > for some reason Jmeter (GUI) stopped running after 5 or 6 hours > yesterday. > > I have 2 thread groups and they were both HTTP client samplers.. with > 100 threads. > > Has anybody run into this situation before? Would a virus scan cause > this type of problem? > > Harry C. Wang > Senior Test Engineer > AOL Mobile (Seattle) > Phone # 206 - 268 - 7502Cell # 425 - 260 - 6891 > AIM CDID hwang98109 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
