+1 But, if you really need to keep most of what you have now, then you might need to tweak the memory usage and the GC policy - because that is what killed the java virtual machine in your case.
On Wed, Oct 26, 2011 at 8:29 AM, Kirk <kirk.pepperd...@gmail.com> wrote: > +1, the listeners will make it look as though there is a leak. Kirk > > On Oct 26, 2011, at 6:24 AM, Deepak Shetty wrote: > > > follow instructions - > > > http://jakarta.apache.org/jmeter/usermanual/best-practices.html#lean_mean > > Dont run GUI mode with listeners that use memory proportional to the > number > > of samples. > > > > Modify the Jmeter startup files to change Xmx to as much memory as you > can > > spare > > > > Its more likely you are using up heap memory than there is a memory leak > > > > regards > > deepak > > > > On Tue, Oct 25, 2011 at 6:58 PM, Dominic <d...@pcdom.com.au> wrote: > > > >> I’m running the attached (unsophisticated) job for some basic figures > to > >> graph the performance of a filtering proxy compared to a direct > connection > >> over time. > >> > >> After 30 minutes jmeter freezes. The CMD box shows the below error: > >> > >> java.lang.OutOfMemoryError: GC overhead limit exceeded > >> Dumping heap to java_pid5276.hprof ... > >> Heap dump file created [517629368 bytes in 3.464 secs] > >> Uncaught Exception java.lang.OutOfMemoryError: GC overhead limit > exceeded. > >> See l > >> og file for details. > >> > >> Anyone know what’s going wrong? > >> > >> Thanks,. > >> > >> Dom > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
