It would be worth upgrading to the latest Java 6 release (31) to see if this fixes the issue.
On 12 April 2012 12:32, MiguelFonseca <[email protected]> wrote: > Yep > > This might be the case :) > > Kind Regards > > On 12 April 2012 12:58, sebb <[email protected]> wrote: >> On 12 April 2012 10:17, MiguelFonseca <[email protected]> wrote: >>> Think its a bug >> >> JMeter does not use any native code, so it's not possible for JMeter >> to cause such a crash. >> This is a not a JMeter bug. >> >> If you are using a 3rd party plugin which uses native code, that could >> be the cause. >> >> Otherwise it's a bug in the JVM (or possibly your OS, I suppose). >> >>> Have this log file from Jmeter: >>> >>> # >>> # A fatal error has been detected by the Java Runtime Environment: >>> # >>> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d8ea473, pid=2172, >>> tid=1572 >>> # >>> # JRE version: 6.0_30-b12 >>> # Java VM: Java HotSpot(TM) Client VM (20.5-b03 mixed mode windows-x86 ) >>> # Problematic frame: >>> # V [jvm.dll+0xfa473] >>> # >>> # If you would like to submit a bug report, please visit: >>> # http://java.sun.com/webapps/bugreport/crash.jsp >>> # >>> >>> :( >> >> If you can reproduce the crash easily, you may wish to report it as above. >> >> >>> Kind Regards, >>> Miguel >>> >>> On 11 April 2012 18:13, sebb <[email protected]> wrote: >>>> On 11 April 2012 16:30, MiguelFonseca <[email protected]> wrote: >>>>> I Guy’s >>>>> >>>>> I was running Jmeter 2.6 r1237317 on a Windows XP 3. >>>>> Microsoft Windows XP [Version 5.1.2600] >>>>> (C) Copyright 1985-2001 Microsoft Corp. >>>>> C:\Documents and Settings\luis.fonseca>java -version >>>>> java version "1.6.0_29" >>>>> Java(TM) SE Runtime Environment (build 1.6.0_29-b11) >>>>> Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode, sharing) >>>>> >>>>> And after a while (10-15 minuts) Jmeter started to kill all threads. >>>>> Repeated the process on other machine and same behavior. >>>>> >>>>> I don’t suspect it was caused by being running this in GUI mode, cause >>>>> I was only simulating 30 users and I was paying attention to task >>>>> manager. >>>>> >>>>> Enough memory and CPU available. >>>>> >>>>> Any hint? >>>> >>>> JMeter does not kill threads unless you tell it to, for example by >>>> setting the Sampler error action "Stop Test" on the Thread Group. >>>> >>>> Check the jmeter.log file to see if there are any relevant messages. >>>> >>>>> Kind Regards, >>>>> Miguel >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >>>> >>> >>> --------------------------------------------------------------------- >>> 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] >> > > --------------------------------------------------------------------- > 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]
