just to add some info, you have to take in account that Jmeter keeps all the sample's result in memory, even i there is no further
process for it.
So, if you are downloading some large objects (like imaging, SW updates and so
on), then you can easily go out of memory.
If this is the case, look for the maximum object size run just few threads and increase memory accordingly (HEAP option, in Jmeter
start script)
HTH
Sergio
Il 20/09/2013 08.02, bobMeliev ha scritto:
When you get this error a file with extension .hprof gets created. This is
the heap dump created when the JVM crashed. This file can be analysed using
Heap Analysis tools to identify the root cause. Ex: You can try analysing
using JHAT (
http://docs.oracle.com/javase/6/docs/technotes/tools/share/jhat.html )
--
View this message in context:
http://jmeter.512774.n5.nabble.com/jmeter-memory-leak-tp4938431p5718206.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]
--
Ing. Sergio Boso
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
