Hi, Thanks for the replies. I have tried all the options you specified like 1.JMeter 2.3.4 version 2.Only one listener there in the scenario(Aggregrate Report). 3.Started jMeter in non-GUI mode. 4.Results logging in CSV format.
But still getting out of memory after 1 hour run duration . But we want to run for 8 hours,Atleast 3-4 hours, Any further suggetions to resolve this? Thanks, Surendar Brett Cave wrote: > > Not sure if this will help, but remove the assertion listener and start up > with "jmeter -l yourtest_report.jtl <more options>" - results will be > logged > to the file. You can specify CSV instead of the default XML via jmeter > properties too which would also improve performance. > > Regards, > Brett > > On Mon, Feb 22, 2010 at 6:20 AM, Jatin Davey <[email protected]> wrote: > >> Try with the latest JMeter Version 2.3.4 >> >> Thanks >> Jatin >> >> >> On 2/21/2010 10:16 PM, TSurendar wrote: >> >>> Hi, >>> >>> Iam using JMeter 2.3.2 for my performance testing requirement. >>> >>> When i run the scenario of 5 scripts (each with around 35 >>> transactions)with >>> 25 users iam getting OOM error. >>> >>> >>> i tried follwing options in a windows macine with 2GB RAM and Solaris >>> machine with 8 GB RAM. >>> >>> 1. Changed Heap size setting to 512, 1024 in JMeter.bat fie. >>> 2.Executed in non-GUI mode. >>> >>> I have added only one aggregrate report listner, removed Assertions, >>> extra >>> listeners. >>> >>> Please help me in resolving this issue. >>> >>> Thanks, >>> Surendar >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- View this message in context: http://old.nabble.com/Out-Of-Memory-issue-tp27676858p27700472.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
